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

Installer does not always add router CA to kubeconfig

XMLWordPrintable

    • Critical
    • Proposed
    • False
    • Hide

      None

      Show
      None
    • NA

      This is a clone of issue OCPBUGS-3214. The following is the description of the original issue:

      Description of problem:

      The installer has logic that avoids adding the router CAs to the kubeconfig if the console is not available.  It's not clear why it does this, but it means that the router CAs don't get added when the console is deliberately disabled (it is now an optional capability in 4.12).
      
      

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

      Seen in 4.12+4.13
      
      

      How reproducible:

      Always, when starting a cluster w/o the Console capability
      

      Steps to Reproduce:

      1. Edit the install-config to set:
      capabilities:
        baselineCapabilitySet: None
      2. install the cluster
      3. check the CAs in the kubeconfig, the wildcard route CA will be missing (compare it w/ a normal cluster)
      
      

      Actual results:

      router CAs missing
      
      

      Expected results:

      router CAs should be present
      
      

      Additional info:

      This needs to be backported to 4.12.
      

            bparees@redhat.com Ben Parees
            openshift-crt-jira-prow OpenShift Prow Bot
            Jinyun Ma Jinyun Ma
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: