-
Notifications
You must be signed in to change notification settings - Fork 3.3k
periodically reload InClusterConfig token #616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
periodically reload InClusterConfig token #616
Comments
Will let you know shortly. I'm working on it. |
@GeekTheGreat are you still working on this? If not, then I would like to take it up. |
Hello @saurav-malani, I'm working on it. |
I would like to work on this issue. |
Hello @isunitha98selvan! I haven't seen any activity on this issue, for the past 4 weeks. Are you still working on this? |
Hello everyone, you can work on it. It is too difficult for me to fix. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Can I work on this issue? @mbohlool |
@LTMenezes please do. |
@LTMenezes are you still working on this? I'd like to give a shot. |
Sorry for the delay @schedutron, I am not, you can go ahead. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
/remove-lifecycle frozen |
this can be closed. @mikedanese |
@zshihang Thanks! |
/close |
@mikedanese: You can't close an active issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
This feature is being implemented for client-go in the main repo and needs to be implemented here too: kubernetes/kubernetes#67359
The text was updated successfully, but these errors were encountered: