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

<4.15>Whereabouts kubeconfig known to expire

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 4.14.z, 4.15.z, 4.17.z, 4.16.z
    • Networking / multus
    • Important
    • No
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Bug Fix
    • In Progress
    • 2/23: telco reviewed

      This is a clone of issue OCPBUGS-50005. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-48745. The following is the description of the original issue:
      —
      Description of problem:

      The whereabouts kubeconfig is known to expire, if the cluster credentials and kubernetes secret changes, the whereabouts kubeconfig (which is stored on disk) is not updated to reflect the credential change

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

      >= 4.8.z (all OCP versions which ship Whereabouts)

      How reproducible:

      With time.

      Steps to Reproduce:

      1. Wait for cluster credentials to expire (which may take a year depending on cluster configuration) (currently unaware of a technique to force a credentials change to the serviceaccount secret token)

      Actual results:

      Kubeconfig is out of date and Whereabouts cannot properly authenticate with API server

      Expected results:

      Kubeconfig is updated and Whereabouts can authenticate with API server

              bpickard@redhat.com Ben Pickard
              openshift-crt-jira-prow OpenShift Prow Bot
              Weibin Liang Weibin Liang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: