Skip to content
You are viewing the documentation for Solo Enterprise for Istio, formerly known as Gloo Mesh (OSS APIs). This version of the documentation is currently under development. Select latest from the version drop down or go to the landing page of the latest stable version.

1.28.0-patch0

Page as Markdown

Solo build of Istio version 1.28.0-patch0 patch release.

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

General Changes

Solo Flavor Changes

  • Added a new CLI option, --data-plane-service-type, to theistioctl multicluster expose command. This option allows specifying a comma-delimited list of the dataplane service types that peers can use to connect with the exposed gateway. Valid values are: loadbalancer or nodeport, with the default being loadbalancer.

  • Added a new CLI option, --preferred-data-plane-service-type, to theistioctl multicluster link command. This option allows specifying the preferred dataplane service type to use when peering with the remote cluster. Valid values are: loadbalancer or nodeport, with the default being loadbalancer.

  • Added support for generating Gateway manifests for multiple contexts at once using istioctl multicluster link --generate.

  • Fixed an issue where traffic would skip local waypoints when there were no healthy endpoints. The traffic will now fail.

  • Fixed an issue when draining is enabled and no cluster name is found. A warning is now issued.

  • Fixed an issue where ServiceInfo events were not propagated after its HboneNodePort field changed. This caused NodePort peering to be broken when a gateway was annotated after its initial creation.

  • Fixed an issue where the status field on Segment resources was not updating.

  • Fixed an issue where the istioctl ecs add-service command incorrectly reported that a task definition did not have an executionRoleArn defined.

  • Removed the explicit requirement for specifying an HBONE listener on an istio-remote gateway resource. If an istio-remote gateway’s preferred dataplane service type is loadbalancer, a network gateway is created with the well-known HBONE port value 15008. Backwards compatibility is maintained by still allowing an HBONE listener to be specified on an istio-remote gateway resource.

FIPS Flavor Changes

No changes in this section.

Last updated on