Kubernetes config not updated when token refreshed

[inikolaev]

I'm using OIDC authentication and running in the the following issue:

OpenIdConnectError: invalid_request (Refresh token is invalid or has already been claimed by another client.)
    at Client.requestErrorHandler (/Users/inikolaev/Projects/kube/node_modules/openid-client/lib/helpers/error_handler.js:16:11)
    at processTicksAndRejections (internal/process/task_queues.js:85:5) {
  error: 'invalid_request',
  error_description: 'Refresh token is invalid or has already been claimed by another client.'
}

After debugging it looks like token is being refreshed correctly the first time, but Kubernetes configuration is not being automatically updated and next time I start application I load old configuration and try to refresh my token using invalid refresh token.

I'm loading configuration from ~/.kube/config and I was expecting it to be updated automatically. I'm not sure is this is how it's supposed to work and if so do you have any pointers on how to update that configuration properly?

[brendandburns]

Unfortunately, the Javascript client library doesn't currently support automatically rewriting the config when it refreshes a token.

There is a utility here:
https://github.com/kubernetes-client/javascript/blob/master/src/config.ts#L352

to call exportConfig() to write the config into a string (which could then be written into a file) so it's possible.

To do it right requires a large-ish refactor of the authenticator interface to include refresh()

[brendandburns]

I'll look into crafting a PR (or probably multiple PRs) to handle this.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.