Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

A helm chart is needed for installing an application on the eheath Platform in a docker container ( Intro to charts ).

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 on 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 default configuration from the chart or to enable/disable feature in the chart.

The values in the values file, is 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: "/"


  • No labels