Home

Welcome to the helm-application wiki!

This project will offer everything needed to host a simple application in Kubernetes, just by writing value files.

The advantage of value files is that's easy to chain them, for example, to have a big common part between integration and production.

This HELM chart is as near as possible to the original Kubernetes files, the major things he does are:

• Transform some list into dict to be able to override them.
• Specific env definition to be able to override them.
• Specific image definition to be able to pin an image to a hash and have the tag in the metadata ConfigMap.
• Add the following standard labels to all the components:
  • app.kubernetes.io/name
  • app.kubernetes.io/instance
  • app.kubernetes.io/component
  • helm.sh/chart
  • app.kubernetes.io/version
  • app.kubernetes.io/managed-by
• Link the components using the standard following labels:
  • app.kubernetes.io/name
  • app.kubernetes.io/instance
  • app.kubernetes.io/component
• Use the name self, self-metadata or self-external on Secret/ConfigMap selector (env and volumes) to select internal Secret/ConfigMap, ConfigMap metadata and respectively secret from external store.
• Automatically used configured Docker registries Secret configuration.
• Be able to create a metadata ConfigMap.

Documentation:

• Images.
• Environment variables.
• Affinity.
• Helpers.

It can create:

• Data:
  • ConfigMap (Example).
  • Secret (Example).
  • ConfigMap metadata (Example).
  • Secret for Docker container registries.
  • External secret (Example).
• Pod:
  • Deployment (Example).
  • CronJob (Example).
  • Job (Example).
  • StatefulSet (Example).
  • PodDisruptionBudget.
• Network:
  • Ingress (Example).
  • Service.
• Monitoring:
  • PodMonitor (Example).
  • Traefik middleware (Example).
• Security:
  • ServiceAccount (Example).

Examples:

• Variable substitution.
• Config container.
• Apache with monitoring.
• Internal or external secrets.

Reference Documentation.