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. 

    4.20

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)

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

Kubeconfig is updated and Whereabouts can authenticate with API server

    This is replication of the bug [https://issues.redhat.com/browse/OCPBUGS-6869.