Changes in 2025 Update 2

View the features, enhancements, and fixes that became available in IBM® Hybrid Cloud Mesh 2025 Update 2 on 6 March 2025.

New features

The following features are included in this Mesh update:

  • You can now update the hostnames or IP addresses for external service endpoints with the Mesh console or the CLI.

    See Connecting to external services.

  • External applications and services are now displayed in the Mesh topology view. You can check whether the applications and services come from a cluster or an external deployment.
    The following screen capture shows an external application called debug2 with an external service called ng-test.
    An external application and service in the topology view

    See Using the IBM Hybrid Cloud Mesh console topology view.

  • Now, you can use the Skupper CLI to expose or unexpose services in Red Hat® Service Interconnect VANs that were previously onboarded to Mesh. The changes are automatically discovered and the updated configuration is applied to the relevant Mesh network segment.

    See Modifying onboarded VANs with the Skupper CLI.

  • When an Open Horizon agent is updated, its certificate and configuration are now also updated. The update only occurs if the agent is not already running with the new version of the certificate and configuration.
  • This update includes some minor enhancements to the topology view. For example, you can now hover over an application to display help that shows whether the application is a cluster-based application or an external application.

Fixed issues

The following issues are fixed in this update:

  • Now, after a Service Interconnect edge gateway is deployed, you can no longer delete the applications and services that the gateway discovers.
  • When you onboard an existing Red Hat Service Interconnect VAN as a Mesh network segment, or you use the Skupper CLI to add a site to an onboarded VAN, the sites now collect initial data within a few minutes. The procedural status of the gateway in the Mesh console changes from Onboarding to Waiting for other gateways.
  • When you redeploy a Service Interconnect edge gateway, now you no longer see a delay before the services are exposed.