deprecated-helm-charts/stable/sealed-secrets

Sealed Secrets

This chart contains the resources to use sealed-secrets.

Prerequisites

• Kubernetes >= 1.9

Installing the Chart

To install the chart with the release name my-release:

$ helm install --namespace kube-system --name my-release stable/sealed-secrets

The command deploys a controller and CRD for sealed secrets on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete [--purge] my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

Parameter	Description	Default
rbac.create	true if rbac resources should be created	true
serviceAccount.create	Whether to create a service account or not	true
serviceAccount.name	The name of the service account to create or use	"sealed-secrets-controller"
secretName	The name of the TLS secret containing the key used to encrypt secrets	"sealed-secrets-key"
image.tag	The Sealed Secrets image tag	v0.7.0
image.pullPolicy	The image pull policy for the deployment	IfNotPresent
image.repository	The repository to get the controller image from	quay.io/bitnami/sealed-secrets-controller
resources	CPU/Memory resource requests/limits	{}
crd.create	true if crd resources should be created	true
crd.keep	true if the sealed secret CRD should be kept when the chart is deleted	true

• In the case that serviceAccount.create is false and rbac.create is true it is expected for a service account with the name serviceAccount.name to exist in the same namespace as this chart before installation.
• If serviceAccount.create is true there cannot be an existing service account with the name serviceAccount.name.
• If a secret with name secretName does not exist in the same namespace as this chart, then on install one will be created. If a secret already exists with this name the keys inside will be used.