When you deploy a workload on Kubernetes, the following happens transparently:
- An Istio sidecar is deployed next to your workload.
- That sidecar is configured with the workload location and other required metadata.
However, when you deploy a workload outside of Kubernetes onto a standalone VM, you have to take care of that by yourself.
The Workload Onboarding feature solves this problem for you out of the box. Using this feature, all you need to do to onboard a workload deployed on a VM into the mesh is:
- Installing an Istio sidecar on the target VM (via DEB/RPM package).
- Install a Workload Onboarding Agent on the target VM (also via DEB/RPM package).
- Provide a minimal, declarative configuration describing where to onboard the workload, e.g.
onboardingEndpoint: # connect to
workloadGroup: # join to
Components and Workflow
The Workload Onboarding consists of the following components:
|Workload Onboarding Operator||the component that is installed into your Kubernetes cluster as part of the TSB Control Plane|
|Workload Onboarding Agent||the component you need to install next to your VM workload|
|Workload Onboarding Endpoint||the component which the Workload Onboarding Agent will connect to register the workload in the mesh and obtain boot configuration for the Istio sidecar|
The following diagram has an overview of the full onboarding flow:
Workload Onboarding Agent executes the onboarding flow according to the declarative
configuration provided by the user.
onboardingEndpoint: # (1)
workloadGroup: # (2)
Given the above configuration, the following takes place:
- The Workload Onboarding Agent will connect to the Workload Onboarding Endpoint
- The Workload Onboarding Endpoint will authenticate the connecting Agent from the cloud-specific credentials of the VM
- The Workload Onboarding Endpoint will decide whether a workload with
such an identity, i.e. the identity of the VM, is authorized to join the mesh in the
WorkloadGroup(2) in particular
- The Workload Onboarding Endpoint will register a new WorkloadEntry at the Istio Control Plane to represent the workload
- The Workload Onboarding Endpoint will generate the boot configuration required to start
Istio Proxy according to the respective
- The Workload Onboarding Agent will save the returned boot configuration to disk and start the Istio sidecar
- The Istio sidecar will connect to the Istio Control Plane and receive its runtime configuration