Uploaded image for project: 'Openshift sandboxed containers'
  1. Openshift sandboxed containers
  2. KATA-4003

[docs] Fix peer pods secret for IBM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • OSC 1.10.0
    • None
    • Documentation
    • None
    • Quality / Stability / Reliability
    • 2
    • False
    • Hide

      None

      Show
      None
    • False

      For IBM, creating/updating a peer pods secret is mandatory because the CCO is not automatically installed.

      Text for Google Cloud, where creating the peer pods secret is optional, was added to the IBM section in MR 411

      ifdef::ibm-cc[]
            = Updating the peer pods secret
            
            You must update the peer pods secret for {cc}.
      
      >>> start of erroneous text
            If the peer pods secret is empty and the Cloud Credential Operator (CCO) is installed, the {osc-operator} uses the CCO to retrieve the secret. If you have uninstalled the CCO, you must update the peer pods secret for {cc} manually or the peer pods will fail to operate.
      >>> end of erroneous text
            endif::[] 

              rhn-support-jowilkin John Wilkins
              apinnick@redhat.com Avital Pinnick
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: