Allow OIDC authentication for kubeconfig clusters when inCluster mode is false #4481
Description
Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.
When running Headlamp with inCluster: false and kubeconfig clusters that use OIDC auth-provider with oidc config. The OIDC login flow works correctly and refresh tokens are cached. However when proxy does requests to kubernetes API the cached token is not used and the headlamp forces to reauthenticate. Headlamp with inCluster mode set to false expects tokens to be stored in the kubeconfig file which is not viable for unique user tokens.
Describe the solution you'd like
The solution is already enabled for inCluster mode set to true, i would like to be able to use the same thing. If removing blocking condition from if statement is not viable it would be nice to have flag (for example --OIDC-USE-COOKIE) to be able to enable this behavior.
What users will benefit from this feature?
- Users with kubeconfigs that contains OIDC auth-provider config
- Users that deployed headlamp in k8s, but do not use inCluster mode
- Users who authenticate with OIDC
- Users that use multiple clusters with the same kubeconfig
Are you able to implement this feature?
No