Files
charts/template
Joseda Rios 91a49eb1e3 Use os-shell in tempate and Jaeger runtime params (#17557)
* Use os-shell in tempate and Jaeger runtime params

Signed-off-by: Joseda Rios <jdrios@vmware.com>

* Update comments in all related files

Signed-off-by: Joseda Rios <jdrios@vmware.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

---------

Signed-off-by: Joseda Rios <jdrios@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
2023-07-11 15:20:03 +02:00
..

Bitnami Charts Template

This directory contains a basic scaffolding to serve as the basis for creating a new chart.

Some of the items that need to be implemented are:

  • commonAnnotations
  • commonLabels
  • imagePullSecret
  • extraDeploy
  • resources.requests
  • resources.limits
  • livenessProbe
  • readinessProbe
  • customLivenessProbe
  • customReadinessProbe
  • podLabels
  • affinity
  • nodeSelector
  • tolerations (that would override the default one)
  • podAnnotations
  • priorityClassName
  • lifecycleHooks
  • sidecars
  • initContainers
  • extraEnvVars
  • extraEnvVarsCM
  • extraEnvVarsSecret
  • command (which would override the default one)
  • args (which would override the default one)
  • extraVolumes
  • extraVolumeMounts
  • updateStrategy
  • podSecurityContext
  • containerSecurityContext

Also it is necessary to use the bitnami/common chart to standarize some of the above items.

⚠️ Take into account this is just an example to follow, depending on the specific use case you will need to remove, add or modify those templates, beyond replacing the placeholders %%FOO%%