Skip to main content

Upgrade Gatekeeper using a Helm Chart

If your applications are deployed using Helm, Corsha provides a Helm Chart you can use to upgrade the Corsha Gatekeeper version and any necessary values.

Our documentation uses Helm Secrets to handle secret material, but reach out to your Corsha TPOC if you could use help with integrating another secrets management method.

Run Helm Upgrade​

note

Ensure you replace $NS with your Kubernetes namespace.

First, edit the values.yaml and secrets.yaml with any updates needed.

Then, run helm upgrade on the Gatekeeper's chart using the version provided by your Corsha TPOC:

helm -n $NS secrets upgrade \
gatekeeper corsha/proxy \
 -f values.yaml -f secrets.yaml \
--verify --version <version>

Verify the Corsha Gatekeeper Upgrade​

Make sure that the Gatekeeper pod terminates and restarts in your namespace. You can do so by running the command below, with output also shown as an example.

$ kubectl  -n $NS get pods
NAME             READY   STATUS        RESTARTS   AGE
<proxy pod name>   1/1     Terminating   0          38s

And then after a couple of seconds it should come back up.

$ kubectl  -n $NS get pods
NAME             READY   STATUS        RESTARTS   AGE
<proxy pod name>   1/1     Running       0         3s

Once the pod is up and running, we can verify the version by running the following command:

kubectl get pod <proxy pod name> -ojson | jq -r '.spec.containers[0].image'
corsha-docker.jfrog.io/proxy:<version>

The version can be found at the end after the colon (ex: <version>).