-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Make the .lock file cross the Read-Modify-Write #28197
Conversation
GCE e2e build/test passed for commit 6495d12. |
Why not lock the entire |
That's tough in this possibly multi-file setup. Could I call |
I think for the short term, we want a lock file per config file held across the entirety of Long term, I'd like to question the usefulness of having multiple config files. @deads2k Given how complicated this code looks, I wouldn't want to keep it without a very good reason. I'm probably just not aware of the use-cases, but I'd like to be enlightened. |
I'm not aware of anyone using it besides @ghodss . @smarterclayton or @bgrant0607 have you see anyone else use multiple kubeconfig files in an env var for merging? |
Here are the issues/use cases for multiple config files - though I'm not sure if this refers to any possibility of multiple files in ~/.kube/, or multiple files spread throughout the file system that get merged together. Multiple files in ~/.kube, like ~/.kube/config and ~/.kube/kubectl: #10693 |
Closing in favor of #28232. |
Opened #28260 to continue the general refactoring discussion. |
Should help prevent concurrent calls to ModifyConfig (with one field changed) from producing an invalid kubeconfig.
We should still eventually rework this to give some stronger semantics around kubeconfig file modification.