Skip to content

Service Helm integration

We use Helm to deploy non-external services to Kubernetes. Such services must provide basic Helm configuration specifying repository source, chart name, chart version. Additionally, a service must provide Helm configuration that specifies yaml path to Helm values that will allow addition of Kubernetes configuration such as:

  • annotations
  • labels
  • environment variables
  • resources
  • sidecars
  • volumes
  • bind mounts

On top of that we expect the Helm chart to support the following values:

  • replicas or replicaCount for scalability
  • fullnameOverride to override hostnames
  • pullPolicy
  • autoscaling
  • image.repository, image.tag, image.registry, image.pullSecrets
  • command
  • args

If you're creating a custom Helm chart we recommend to fork one of existing charts by Wodby or by Bitnami

Helm chart information defined under helm section in a service template.