You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a KubernetesClientwrapper class in Control Panel, that attempts use a users ID token as its auth credential when making API calls. I am not sure that this is working as intended, so we should spend some time to dig a bit deeper about:
What the original intention of using a users ID token was rather than the service accounts credentials
How this is intended to work and determine if this is working or not
Amend the implementation as necessary
To Reproduce
Run the control panel locally
Update the code where the KubernetesClient is used (e.g. tool restart) and pass an arbritary string rather than a real ID token
Trigger the action in the browser (e.g. tool restart)
If the restart triggers successfully, this indicates the ID token being passed in the KubernetesClient is irrelevant
Expected Behaviour
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug.
There is a
KubernetesClient
wrapper class in Control Panel, that attempts use a users ID token as its auth credential when making API calls. I am not sure that this is working as intended, so we should spend some time to dig a bit deeper about:To Reproduce
KubernetesClient
is used (e.g. tool restart) and pass an arbritary string rather than a real ID tokenKubernetesClient
is irrelevantExpected Behaviour
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: