Hello all,
During the latest SIG-CLI meeting, we discussed the following PR:
One of the issues brought up during discussions was the introduction of a new dependency in client-go. On the call, we determined that we could easily reimplement that functionality without the additional dependencies.
However, the question was also asked if we wanted to remove file locking entirely, since the general guidance is to not make concurrent changes to kubeconfig. The goal here is to get some feedback from the community on whether we should continue to support file locking via a more robust and atomic mechanism, or should we phase out file locking kubeconfig entirely.
Please let me know your thoughts. Thanks,
Ross