Changes in 2024 Update 9

View the features, enhancements, and fixes that became available in IBM® Hybrid Cloud Mesh 2024 Update 9 on 16 December 2024.

2024 Update 9

The following features are included in this Mesh update:

  • You can now onboard your existing Red Hat® Service Interconnect VANs as Mesh network segments. All gateways, applications, and services in your VANs are onboarded to Mesh. Mesh connection policies are generated that represent how the services are exposed in the VANs.
    After a VAN is onboarded, you can monitor and manage the VAN and its resources in Mesh. In the topology view, you can view metrics about the traffic between the applications and services in the VAN.
    Restriction: If you modify a VAN by using the Skupper CLI, while the VAN is onboarding or after the onboarding completes, the changes are not shown in Mesh.

    To monitor the onboarding progress, click Onboard network segment on the Network segments page in the Mesh console.

    The following screen capture shows an example of a Red Hat Service Interconnect VAN that is onboarding to Mesh.
    Onboarding network segments page
    See Onboarding VANs as Mesh network segments.
  • Events are now created during the automatic upgrade of a Mesh agent. When the agent starts to upgrade, an event of minor severity is created for the associated gateway and this event is cleared when the upgrade completes successfully. If an upgrade fails, an event of major severity is created, and this event is cleared when the upgrade completes successfully. For more information about Mesh events, see Events.
  • The version of Red Hat Service Interconnect that is installed when you deploy a gateway is now 1.8.1. Your existing 1.4.x gateways are not upgraded automatically. To upgrade a gateway, you must delete the gateway and deploy it again. For more details, see Deleting Service Interconnect edge gateways with the Mesh console and Deploying and connecting Service Interconnect edge gateways by using the Mesh console.

    This updated version of Red Hat Service Interconnect also makes some additional capabilities available for those who upgrade. For more information on this updated Red Hat Service Interconnect version, see Red Hat Service Interconnect documentation.

  • When you create a connection policy, you now have more granular control over the namespaces that a service is exposed to. You can now connect a service to applications in specific namespaces in the network segment or to the entire network segment.

    See Creating connection policies by using the Mesh console and Creating connection policies by using the Mesh CLI.

Fixed issues

The following issues are fixed in this update:

  • Users were able to use the palmctl to erroneously create a connection between gateways in different network segments. The CLI was fixed to validate that both gateways in the remote connection are in the same network segment
  • The statuses of gateways now match between the Mesh console and the palmctl CLI.
  • Gateways no longer go from an operational state to an unreachable state with a loss of connectivity between the gateway and Mesh.
  • The discovery of applications and services by the Mesh console no longer times out.
  • Before this update, if autodiscovered applications were deactivated in Kubernetes or Red Hat OpenShift® Container Platform, they remained in Mesh. Now, applications that are deactivated no longer remain in Mesh.
  • Gateways can be deleted and recreated without the need to recreate connection policy.