Release Notes
Version 1.11.0-dev
- In the Service Registry, values previously found in the
ExternalAddresses
andHostnames
fields are now returned in theHostnames
andInternalHostnames
fields, respectively. TheExternalAddresses
field now contains a list of IPs or load balancer hostnames that can be used to reach the service from outside the mesh. - The STRICTER propagation for WASM extensions from all Security Settings has been changed so that it is not accumulative. Instead, the WASM Extension collection applied in a parent resource will overwrite their children's. This is more secure and gives more control to privileged users on the extensions that can be used in the different workspaces.
- By default, new clusters will use LOCAL namespace scoping if no other scope is specified. This default setting is chosen because most use cases do not involve cross-cluster applications. As a result, the service registry will provide a more accurate view of the services within the mesh. Note: You can always update the namespace scoping by modifying the Cluster resource.