v0.14.1

Release Notes

Please read the RELEASE_NOTES which contain among other things important information for who is upgrading from previous releases.

Install

Client side

Install client-side tool into /usr/local/bin/:

• Linux x86_64:

wget https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.14.1/kubeseal-linux-amd64 -O kubeseal
sudo install -m 755 kubeseal /usr/local/bin/kubeseal

• Macos: (might lag a few hours behind a new release, this icon will reflect that latest release)

brew install kubeseal

• Other OS/arch: you might find binaries for your OS/arch combo attached to this release below.

Cluster side

Install SealedSecret CRD, server-side controller into kube-system namespace.

$ kubectl apply -f https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.14.1/controller.yaml

NOTE: If you can't (or don't want) to use the kube-system namespace, please consider this approach

NOTE: if you want to install it on a GKE cluster for which your user account doesn't have admin rights, please read this

NOTE: since the helm chart is currently maintained elsewhere (see https://github.com/helm/charts/tree/master/stable/sealed-secrets) the update of the helm chart might not happen in sync with releases here.

v0.14.0

Release Notes

Please read the RELEASE_NOTES which contain among other things important information for who is upgrading from previous releases.

Install

Client side

Install client-side tool into /usr/local/bin/:

• Linux x86_64:

wget https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.14.0/kubeseal-linux-amd64 -O kubeseal
sudo install -m 755 kubeseal /usr/local/bin/kubeseal

• Macos: (might lag a few hours behind a new release, this icon will reflect that latest release)

brew install kubeseal

• Other OS/arch: you might find binaries for your OS/arch combo attached to this release below.

Cluster side

Install SealedSecret CRD, server-side controller into kube-system namespace.

$ kubectl apply -f https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.14.0/controller.yaml

NOTE: If you can't (or don't want) to use the kube-system namespace, please consider this approach

NOTE: if you want to install it on a GKE cluster for which your user account doesn't have admin rights, please read this

NOTE: since the helm chart is currently maintained elsewhere (see https://github.com/helm/charts/tree/master/stable/sealed-secrets) the update of the helm chart might not happen in sync with releases here.

helm-v1.14.0-r1

Helm chart for the sealed-secrets controller.

(this GH release is marked as pre-release so it doesn't get confused with the Sealed Secrets main releases; it's still a real helm chart release)

helm-v1.13.2-r2

A Helm chart for Sealed Secrets.

(this GH release is marked as pre-release so it doesn't get confused with the Sealed Secrets main releases; it's still a real helm chart release)

sealed-secrets-1.13.2

A Helm chart for Sealed Secrets

NOTE: this is just a release tag for the helm chart, this is not a new release of the sealed-secrets controller itself!

TODO: change the tag naming scheme to make this more obvious

sealed-secrets-1.13.1

A Helm chart for Sealed Secrets

v0.13.1

Release Notes

Please read the RELEASE_NOTES which contain among other things important information for who is upgrading from previous releases.

Install

Client side

Install client-side tool into /usr/local/bin/:

• Linux x86_64:

wget https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.13.1/kubeseal-linux-amd64 -O kubeseal
sudo install -m 755 kubeseal /usr/local/bin/kubeseal

• Macos: (might lag a few hours behind a new release, this icon will reflect that latest release)

brew install kubeseal

• Other OS/arch: you might find binaries for your OS/arch combo attached to this release below.

Cluster side

Install SealedSecret CRD, server-side controller into kube-system namespace.

$ kubectl apply -f https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.13.1/controller.yaml

NOTE: If you can't (or don't want) to use the kube-system namespace, please consider this approach

NOTE: if you want to install it on a GKE cluster for which your user account doesn't have admin rights, please read this

NOTE: since the helm chart is currently maintained elsewhere (see https://github.com/helm/charts/tree/master/stable/sealed-secrets) the update of the helm chart might not happen in sync with releases here.

v0.13.0

Release Notes

Please read the RELEASE_NOTES which contain among other things important information for who is upgrading from previous releases.

Install

Client side

Install client-side tool into /usr/local/bin/:

• Linux x86_64:

wget https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.13.0/kubeseal-linux-amd64 -O kubeseal
sudo install -m 755 kubeseal /usr/local/bin/kubeseal

• Macos: (might lag a few hours behind a new release, this icon will reflect that latest release)

brew install kubeseal

• Other OS/arch: you might find binaries for your OS/arch combo attached to this release below.

Cluster side

Install SealedSecret CRD, server-side controller into kube-system namespace.

$ kubectl apply -f https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.13.0/controller.yaml

NOTE: If you can't (or don't want) to use the kube-system namespace, please consider this approach

NOTE: if you want to install it on a GKE cluster for which your user account doesn't have admin rights, please read this

NOTE: since the helm chart is currently maintained elsewhere (see https://github.com/helm/charts/tree/master/stable/sealed-secrets) the update of the helm chart might not happen in sync with releases here.

v0.12.6

Release Notes

Please read the RELEASE_NOTES which contain among other things important information for who is upgrading from previous releases.

Install

Client side

Install client-side tool into /usr/local/bin/:

• Linux x86_64:

wget https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.12.6/kubeseal-linux-amd64 -O kubeseal
sudo install -m 755 kubeseal /usr/local/bin/kubeseal

• Macos: (might lag a few hours behind a new release, this icon will reflect that latest release)

brew install kubeseal

• Other OS/arch: you might find binaries for your OS/arch combo attached to this release below.

Cluster side

Install SealedSecret CRD, server-side controller into kube-system namespace.

$ kubectl apply -f https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.12.6/controller.yaml

NOTE: If you can't (or don't want) to use the kube-system namespace, please consider this approach

NOTE: if you want to install it on a GKE cluster for which your user account doesn't have admin rights, please read this

NOTE: since the helm chart is currently maintained elsewhere (see https://github.com/helm/charts/tree/master/stable/sealed-secrets) the update of the helm chart might not happen in sync with releases here.

v0.12.5

Release Notes

Please read the RELEASE_NOTES which contain among other things important information for who is upgrading from previous releases.

Install

Client side

Install client-side tool into /usr/local/bin/:

• Linux x86_64:

wget https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.12.5/kubeseal-linux-amd64 -O kubeseal
sudo install -m 755 kubeseal /usr/local/bin/kubeseal

• Macos: (might lag a few hours behind a new release, this icon will reflect that latest release)

brew install kubeseal

• Other OS/arch: you might find binaries for your OS/arch combo attached to this release below.

Cluster side

Install SealedSecret CRD, server-side controller into kube-system namespace.

$ kubectl apply -f https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.12.5/controller.yaml

NOTE: If you can't (or don't want) to use the kube-system namespace, please consider this approach

NOTE: if you want to install it on a GKE cluster for which your user account doesn't have admin rights, please read this

NOTE: since the helm chart is currently maintained elsewhere (see https://github.com/helm/charts/tree/master/stable/sealed-secrets) the update of the helm chart might not happen in sync with releases here.