Skip to main content

Cert-manager upgrade in Konvoy 1.6.0 fails if Kommander is disabled

Steven Sylvester
  • Updated

Overview

When upgrading from a previous Konvoy version to 1.6.0, you might find that the cert-manager upgrade fails if Kommander is not enabled in your upgraded cluster.
This has been fixed in Konvoy 1.6.1, so you should avoid this issue by upgrading directly to that version.

If you've encountered it on an upgrade to 1.6.0, however, use the following workaround:
 

Workaround

If cert-manager is failing after an upgrade to 1.6.0, create a cert-manager-upgrade-restore.yaml file with the following job definition: 
apiVersion: batch/v1
kind: Job
metadata:
  namespace: cert-manager
  name: cert-manager-upgrade-restore
spec:
  template:
    spec:
      serviceAccountName: cert-manager-upgrade
      containers:
        - name: cert-manager-upgrade
          image: mesosphere/kubeaddons-addon-initializer:v0.4.2
          command: [""cert-manager-upgrade"", ""restore""]
          env:
            - name: ""CERT_MANAGER_NAMESPACE""
              value: cert-manager
      restartPolicy: Never
  ttlSecondsAfterFinished: 900

Run the job with "kubectl apply -f cert-manager-upgrade-restore.yaml" and it should resolve the issue.

If not, please create a support ticket describing the problem and we'll be happy to help:
https://support.d2iq.com/s/article/Opening-a-New-Support-Case