Automatic updating of imported cluster configs about kube-forwarder

[lnikell]

Hi @dbarentine, we will read more about how OIDC works, so if I understand you correctly there is external sort of daemon that refreshes your token in kubeconfig periodically.

[dbarentine]

@lnikell Yeah essentially. It's not so much a daemon but a webook token authentication that gets called when you try to make an authenticated call via kubectl.

This causes one of two things to happen:

1. It forces an authentication (in our case using Microsoft's device login)
2. It transparently refreshes the token using the refresh_token in the configuration.

Both result in an updated .kube/config file as the access-token value will be updated. Token expiration I think is 60 minutes so our .kube/config will be updated every 60 minutes if we are actively working with kubectl.

For more information, you can see the AAD Integration here: https://docs.microsoft.com/en-us/azure/aks/concepts-identity#azure-active-directory-integration

Or the Webhook Token Authentication here: https://kubernetes.io/docs/reference/access-authn-authz/authentication/#webhook-token-authentication

[lnikell]

@dbarentine Thank you for clarification, we will try to come up with solution for that.

[proAlexandr]

Hi, @dbarentine. We have released a new version. Now it's possible to set a path to a file instead of copying its content. I hope the feature will fix your issue. Please, feel free to try the update and share feedback with us. Thanks!

[lnikell]

Closing the issue, It should be resolved in the latest version as Alexandr mentioned.