Investigate why users are not being able to authenticate to cluster even after regenerating kubeconfig file through Kuberos

[kyphutruong]

Background

We've had many reports of users not being able to authenticate to the cluster after regenerating the kubeconfig file through Kuberos.

The workaround at the moment is to delete the user from Auth0 and then reauthenticating through Kuberos.

Examples of raised issues in Slack:
https://mojdt.slack.com/archives/C57UPMZLY/p1735032951002559
https://mojdt.slack.com/archives/C57UPMZLY/p1732544758553179

Proposed user journey

Users should be able to authenticate to cluster without having to delete their auth0 profile.

Approach

Test authenticating journey with test user and fix or streamline

Which part of the user docs does this impact

Connecting to the Cloud Platform’s Kubernetes cluster

Communicate changes

• post for #cloud-platform-update
• Weeknotes item
• Show the Thing/P&A All Hands/User CoP
• Announcements channel

Questions / Assumptions

Definition of done

• readme has been updated
• user docs have been updated
• another team member has reviewed
• smoke tests are green
• prepare demo for the team

Reference

How to write good user stories