-
Story
-
Resolution: Done
-
Medium
-
None
SO CNFM Helm Client Process for AS Deployment
- For the initial PoC, the Helm Client will be used as a SO CNF Southbound plugin for interfacing with K8S Cluster(s)
- An ASD can contain multiple DeploymentItems (which are corresponding Helm Charts). To determine the order of Helm Chart executions, the deploymentOrder from the ASD>DeploymentItems will be used.
- Based on the deploymentOrder, the SO CNFM Helm Client does:
- From the registered K8S Clusters, choose a target K8S cluster name
- With the helm command with --kubeconfig or kube-contenxt option, set the target K8S cluster to work with.
- Invoke the helm install command towards the target K8S cluster, passing the release name, enhanced helm chart and custom values file.
- Create a unique release name with the helm chart name prefix
- Store the release name to the as_instance object/database
- e.g., helm install <release> <chart> --kubeconfig ~/.kubeconfigs/<cluster_name>.kubeconfig
Post Condition:
- Helm Chart(s) under an ASD are deployed in the target K8S Cluster
- mentioned in
-
Page Loading...