-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Improve parallel run reliability by putting lock on files before writing #5075
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: medyagh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a solid refactor. Thank you!
Hopefully closes start race: x509: certificate is valid for <ips>, not <ip> #4967 and maybe http: TLS handshake error from 127.0.0.1:58378: remote error: tls: bad certificate #5040
Provide a decorative wrapper arround ioutil.WriteFile that locks the file before writing
Provide more reliable parallel minikube experience by locking write file for following operations:
-- minikube config
-- profile config
-- cert generation
-- notify write time
-- kubeconfig update
-- mount file
-- extract
Added Exponential Retry logic for acquiring the lock (retry up to 13 seconds)
Converted all the retry across minikube codebase to exponential retry
NOTE1: this lock mechanism is only respected by minikube binaries. not by other procs in the OS.
(which is mostly okay!)