Kubernetes Participant performs the helm chart installation and LCM for k8s microservices that take part in Control loop. It implements Participant-Intermediary to receive events from DMaap and interact with Helm CLI.
It acts as a wrapper around Helm Cli to manage helm charts and K8s pods deployed in the cluster.
Helm 3 overview:
In Helm3, helm cli acts as a interface to connect with Kubernetes cluster to deploy and manage helm charts. It also supports configuring multiple chart repositories to the helm client and access those charts for installation. The repositories can be a local chart server running on the same machine as well a third party chart server running elsewhere. The URL of the chart server is configured to the helm repo list to access the hosted charts. User can add a repository and push helm charts under the repository to be accessed during installation.
Example: configured chart repos and the available charts are listed via helm cli:
Kubernetes Participant Architecture in Istanbul:
In Istanbul release, Kubernetes participant in control loop supports installation of charts in the below ways:
- Installing a helm chart that is present in the local file system where the kubernetes participant is hosted.
- Installing any charts from the repositories that are configured on the helm client.