Problems or challenges CI/CD pipeline of k8s
- Consider a normal CI/CD pipeline where the builds are triggered once in a day (nightly builds) and we need to create 3 environments
- Sample deployment manifest for two days
- The problem with k8s manifests are they are static and do not support dynamic manifest files, we need some external way to create them
- Then, we have two possible solutions now
- helm (package manager for k8s) Refer Here
- Kustomize Refer Here
Helm
- If you consider kubernetes as Operating system, Helm is a package manager (apt, yum , choco, brew)
- In Helm’s vocubalary, package is a
chart - How Helm Works
- Helm installation Refer Here for script based installation on linux
- Lets setup helm autocompletion Refer Here
source <(helm completion bash)
echo "source <(helm completion bash)" >> ~/.bashrc
- Basic Terms in Helm
- Chart (Package)
- Chart Repository: When it comes to sharing charts, Helm describes a standard format for indexing and sharing information about helm charts. A Helm chart repository is simply a set of files, reachable over network that confirms to helm specification
- Easiest way to find popular chart repository is Artifact Hub Refer Here
Helm chart components at a high level
- Create a helm chart
helm create hello-world
- Refer Here for the changes
