Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-10828

[enterprise-4.12] Issue in file security/cert_manager_operator/cert-manager-operator-uninstall.adoc

XMLWordPrintable

    • No
    • 2
    • OSDOCS Sprint 234, OSDOCS Sprint 235, OSDOCS Sprint 237, OSDOCS Sprint 236
    • 4
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      some details for the upgrade are missing

      Version-Release number of selected component (if applicable):

       

      How reproducible:

       

      Steps to Reproduce:

      Please add following steps like:
      
      - if you have a external Issuer types you need to uninstall this external issuer before you delete cluster operator.
      
      - you have to make sure that you have a backup of all existing issuer, clusterissuer, and certificates. Or at least they are recreated by some gitops features.
      you can get a list of the existing objects by:
      $ oc get issuers.cert-manager.io -A
      NAMESPACE      NAME                               READY   AGE
      cert-manager   letsencrypt-issuer                 True    19h
      $ oc get clusterissuers.cert-manager.io -A
      NAME                        READY   AGE
      letsencrypt-clusterissuer   True    19h
      $ oc get certificates.cert-manager.io -A
      NAMESPACE           NAME                                  READY   SECRET                                AGE
      kafka               my-cluster-certificate                True    my-cluster-certificate                18h
      ...
      
      Additioninal question:
      what's about the certmanagers.config.openshift.io, shouldn't it be deleted as well.

       

      Actual results:

       

      Expected results:

       

      Additional info:

       

            sdudhgao@redhat.com Servesha Dudhgaonkar
            rbaumgar Robert Baumgartner
            Xingxing Xia Xingxing Xia
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: