Changes in 2024 Update 3

View the features, enhancements, and fixes that became available in IBM® Hybrid Cloud Mesh 2024 Update 3 on 5 April 2024.

2024 Update 3

The following features are included in this Mesh update:

You can now use the Mesh CLI and API to filter events by resource type. For more information about working with events, see Events.
You can deploy Red Hat® Service Interconnect gateways in ARO environments. For more information, see Installing an Open Horizon agent.
You can now register a gateway directly from the Gateways page. Click Register gateway, select the gateway type, select the network segment and agent, and then select the cluster. After you submit these details, the namespace is created, the gateway is registered, and then the namespace is updated with the gateway details.
When you register a service in a namespace that is managed by Red Hat Service Interconnect, the extension palmetto.ibm.com is no longer appended to the service name. For example, a service is now called backend instead of backend.palmetto.ibm.com. It is now easier to use the topology view in the Mesh console because the service names are shorter.

The following issues are fixed in this update:

When you deploy an Service Interconnect edge gateway, the message [ERROR] internal error is returned.
On the Gateways page, the search and filter functions don't work in card view.
In the topology view, connection lines between applications and services are not displayed.
When Mesh discovers a new service, a new deployment is created with its instances and endpoints, but the service record is also deleted and re-created. If a policy related to the new deployment exists, the new deployment is not published.