-
it is package manager
-
Create new charts from scratch
-
Package charts into chart archive (tgz) files
-
Interact with chart repositories where charts are stored
-
Install and uninstall charts into an existing Kubernetes cluster
-
Manage the release cycle of charts that have been installed with Helm
- Local chart development
- Managing repositories
- is the service that actually communicates with the Kubernetes API to manage our Helm packages.
- RBAC https://docs.helm.sh/using_helm/#tiller-and-user-permissions
- at leat 2 steps
-
- step create docker files ( 1 or more, in the worst case N where N is number of apps )
- start with alpine linux
- so we have dockerfile (container)
- container goes to artifactory docker repository
-
- use docker containers within Kubernetes Helm Charts
- you start with appp container (image)
- using Helm create from templates Charts for apps (?? not sure how many , in best case one parametrized resusable template, maybe N where N is nubmer of apps)
- this functionality will do Jenkins ( heml cli or ku .. ) or our REST Spring Boot service
- Charts should go to artifactory HElm repository + Here Container Repository
-
helm templates (functions, pipelines, values, objects, flow control, variables, named templates, include, files, subcharts)
-
Canary build, Canary Charts
-
https://docs.helm.sh/using_helm/#tiller-and-user-permissions
-
info o 2 JWT iclic + credentials