Integrating non-Kubernetes workloads
Use IBM® Hybrid Cloud Mesh (Mesh) to connect your Kubernetes and non-Kubernetes client applications and services over the Mesh network segment. The non-Kubernetes applications and services can run on infrastructure such as VMs, mainframes, load balancers, and bare metal servers.
| Term | Definition |
|---|---|
| External client | A client application that operates outside of a Kubernetes cluster but can connect to services within a Mesh network segment. |
| External service | A service that operates outside of a Kubernetes cluster but can be accessed by applications within a Mesh network segment. |
| Service entry point | An IP address and port on the local network that external clients use to connect to a service. |
Mesh enables seamless connectivity between your Kubernetes and non-Kubernetes workloads, regardless of their deployment environment. You don’t need to migrate your existing non-Kubernetes workloads to Kubernetes to enable them to connect over the Mesh network segment. For example, Mesh enables a front-end application that runs on a VM in an on-premises environment to communicate with a backend service on a cloud-based Kubernetes cluster.
Mesh also supports the migration of external clients and services into Kubernetes, reducing application downtime and helping to ensure a smooth transition.