Resolve "Update certmanager to versison 0.4.x"
This is a breaking change. Either re-deploy entirely, or kubectl scale --namespace <deployment-namespace> --replicas=0 deployment <cert-manager-deployment-name>
.
In the case of my test cluster:
kubectl scale --replicas=0 deployment certmanager-gitlab
helm dep update
helm upgrade gitlab . -f config.yaml
I tested the ability of generating new certificates after update by using kubectl delete secrets gitlab-gitlab-tls gitlab-registry-tls gitlab-minio-tls
, while monitoring kubectl get pods -lrelease=gitlab --watch
. This showed multiple Pods named cm-acme-http-solver-xxxxx
being started/stopped, and then my GitLab instance URL functioned as expected and the secrets were recreated.
Side effect: deployment name has changed from certmanager-gitlab
to gitlab-certmanager`.
Changes
certmanager: Update requirements.yaml
to use cert-manager
v0.4.0
certmanager-issuer: update to ACMEv2 endpoint for Let's Encrypt
Per https://cert-manager.readthedocs.io/en/release-0.4/admin/upgrading/upgrading-0.2-0.3.html#removing-support-for-acmev1-in-favour-of-acmev2, Update the endpoint of certmanager-issuer to the ACMEv2
Closes #617 (closed)