release-v1.1.1-1
Notable Changes
- Circuit breaking support for traffic directed to in-mesh and external destinations
- A new
spec.sidecar.localProxyMode
field in the MeshConfig API allows users
to specify whether traffic from Envoy sidecars to application containers is
redirected via127.0.0.1
(the previous behavior and current default) or the
Pod's IP address - A new
spec.traffic.networkInterfaceExclusionList
field in the MeshConfig API
allows users to specify names of network interfaces on Pods that should not
have traffic proxied through Envoy sidecars - The installed MeshConfig resource can now be updated with
kubectl apply
Breaking Changes
The following changes are not backward compatible with the previous release.
- The
osm_proxy_response_send_success_count
andosm_proxy_response_send_error_count
metrics are now labeled with the proxy certificate's common name and XDS type, so queries to match the previous equivalent need to sum for all values of each of those labels.
Deprecation Notes
The following capabilities have been deprecated and cannot be used.
- The
osm_injector_injector_sidecar_count
andosm_injector_injector_rq_time
metrics have been removed. Theosm_admission_webhook_response_total
andosm_http_response_duration
metrics should be used instead. - OSM will no longer support installation on Kubernetes version v1.19.
CRD Updates
- No CRD changes between tags v1.0.0-1 and v1.1.1-1