Files
charts/template
Javier J. Salmerón-García 91c707c9e4 [bitnami/*] ci: 👷 Add tag and changelog support (#25359)
* [bitnami/*] chore: 👷 Add tag and changelog support

Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>

* perf:  Avoid fetching the index branch

Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>

* chore: 🔧 Do not scan CHANGELOG.md files

Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>

* chore: 🙈 Update .helmignore files

Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>

* refactor: ♻️ Separate push-tag section

Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>

---------

Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com>
2024-05-21 10:24:21 +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)
  • daemonsetAnnotations
  • deploymentAnnotations
  • statefulsetAnnotations
  • 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%%