-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.8.z
-
Important
-
None
-
Plumbing Sprint 233, Plumbing Sprint 234, Plumbing Sprint 235, Plumbing Sprint 236
-
4
-
Rejected
-
False
-
-
Bug Fix
-
Bug Fix
-
In Progress
-
Customer Escalated
-
-
2/23: telco reviewed
-
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
