Helm Charts
- Frederik Mogensen (Unlicensed)
- John Schneider
A helm chart is needed for installing an application on the eHealth Platform in a docker container ( Helm | ).
This helm chart will be supplied by the Platform and will among other things define:
Containers
How to deploy a container to the Kubernetes environment
How to monitor if the container is ready to receive requests and if it is still alive
Which ports to send requests to
How much resources the container is expected to use, and how much it is allowed to use in total
Service Discovery
Which DNS name to reach the application on (internally on the cluster)
Which version of the application to send requests to
Ingress
Which DNS name and path to reach the application from the internet (if any)
Which port to receive requests on
Rewrite paths if needed
Configuration
The chart can be configured with a values file in yaml format. This file can be used to override the default configuration from the chart or to enable/disable features in the chart.
The values in the values file are dependent on the chart. But an example could be the following:
image: "my-new-service"
imageTag: "v1.0.2"
component: "my-new-service"
appVersion: "1.0.0"
containerPort: 80
ingress:
hostname: myservice.$ENV_BASEURL
livenessProbe:
httpPath: "/"
readinessProbe:
httpPath: "/"
See also