Changes in 2025 Update 1

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

New features

The following features are included in this Mesh update:

  • You can now use Mesh to connect applications that run on Kubernetes with services that run on non-Kubernetes infrastructure like VMs, bare metal servers, SaaS services, or mainframes. You use external services to make these connections. An external service is a service that operates outside of a Kubernetes cluster, which applications within a Mesh network segment can access. You don’t need to migrate your existing services to Kubernetes for Mesh to connect to them.

    To connect your Kubernetes-based applications with external services, you register an application, register an external deployment, and then register service endpoints for the external service.

    The following screen capture shows an application that has four service endpoints with target hostnames and IP addresses.

    Registering external services
    See Connecting to external services.
  • You can now use the Skupper CLI to modify Red Hat® Service Interconnect VANs that were previously onboarded as Mesh network segments. The changes are automatically discovered and the updated configuration is applied within Mesh.
    You can use the Skupper CLI to make the following changes:
    • Add a Red Hat Service Interconnect site to the VAN.
    • Add or delete links between the sites in the VAN.
    Restriction: If you use the Skupper CLI to delete a site from the VAN, the changes are not discovered or shown in Mesh.

    See Modifying onboarded VANs with the Skupper CLI.

  • An information event is created when a new version of an Open Horizon agent is available. For more information about Mesh events, see Events.
  • Mesh can now automatically discover pods that are managed by KubeVirt in your Kubernetes environment.

Fixed issues

The following issues are fixed in this update:

  • You can now delete a gateway even if it is connected to a namespace.
  • You can no longer register a location under a cloud when autodiscovery mode is on.
  • Some events indicate that a gateway is unreachable. These events are now deduplicated.
  • The association of a gateway with a namespace now always occurs after the initial contact with the Mesh agent. This change means that the gateway doesn’t get stuck in a Ready to deploy procedural status, but moves to the correct status.
  • When you use the CLI to unlink a gateway from a namespace, the procedural status of the gateway no longer gets stuck at In progress status.
  • When you create a second connection policy or any subsequent policies and the Entire network segment button in the Network segment options area is selected, the Save button is now available.
  • When you use the CLI to uninstall an Open Horizon agent, the confirmation message that is displayed is now clearer.
  • If a gateway becomes unreachable, an event is now generated.
  • When you create a connection policy, and select to include the entire network segment as the partition to connect from, click Save, then try to create another connection policy, the Create policy button on the Connection policies page is now available.
  • The dashboard configuration file that is provided in the documentation for Service Interconnect edge gateways is now updated and valid. See Service Interconnect edge dashboard configuration file.