This release note describes what’s different between Solo builds of Istio versions 1.27.1 and 1.27.1-patch1.

General Changes

Solo Flavor Changes

  • Improved the experience when using istioctl multicluster check against installations <1.27 by checking the gloo.solo.io/PeeringSucceeded remote gateway condition.

  • Fixed if a Service only exists in the remote cluster, the local cluster will now be able to apply L7 policy via a local sidecar or waypoint, as long as the remote Service properly declares an L7 protocol via the port name or appProtocol.

  • Fixed Services with solo.io/service-scope=global-only will now be reachable via standard Kubernetes service hostnames whether the local cluster has a copy of the service or not.

  • Fixed istiod crash when supplying a license to a FIPS-compliant version using a license secret.

  • Fixed deleting a remote service did not delete the corresponding service entry in the local cluster.

  • Fixed multi-cluster traffic breaking when each cluster uses a different trust domain.

  • Fixed to-workload traffic through a waypoint failing when peering is enabled (regardless of actual multi-cluster installation or traffic).

  • Fixed traffic routing through the local cluster’s waypoint proxy when a service exists only on remote cluster, but the same waypoint is also deployed locally. Traffic now correctly routes to remote waypoint proxies when the service only exists remotely.

  • Fixed rare istiod crash when using multi-cluster ambient with waypoints.

  • Fixed traffic breaking when a waypoint from the local cluster is deleted while one still exists on the remote cluster.

FIPS Flavor Changes

No changes in this section.