...
- Kubernetes cluster running.
- Helm CLI running.
- Currently, the operator is expected to either store the Helm charts in any of the configured Helm repositories via Helm CLI commands or ensure that the charts are available on the local storage directory of kubernetes-participant. (This directory is a preconfigured path specified on the participant config that acts as a local chart repository).
Note: When using the Kubernetes participant is containerized in the upcoming releasein docker container, the kubeconfig file of the required kubernetes cluster should be copied to the k8s-participant's docker container in order to make the Helm CLI work with the external cluster.
...
In the Istanbul release, the CLAMP Kubernetes participant supports the following methods for installation of helm charts via CLAMP:
- Installation of a Helm chart that is present in the same local file system as where the kubernetes participant is hosted
- Installation of Helm charts from the Helm repositories that are configured on the Helm client
...
The Kubernetes participant receives messages through the participant-intermediary common code, and handles them by invoking the Kubernetes Open API via the Helm client. For example, When a ControlLoopUpdate message is received by Kubernetes participant, the control loop element state changed from UNINITIALIZED to PASSIVE, Kubernetes-participant triggers Kubernetes Open API and passes the HELM charts towards cluster.
Run CLAMP Kubernetes Participant command line using Maven
mvn spring-boot:run -Dspring-boot.run.arguments="--topicServer=localhost"
Run CLAMP Kubernetes Participant command line using Jar
java -jar -DtopicServer=localhost target/policy-clamp-participant-impl-kubernetes-6.1.2-SNAPSHOT.jar