-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
fix: remove duplicate line in known_hosts when minikube deletes #16965
base: master
Are you sure you want to change the base?
fix: remove duplicate line in known_hosts when minikube deletes #16965
Conversation
Hi @ComradeProgrammer. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Can one of the admins verify this patch? |
you might need to rebase and ensure you are logged in |
f60898c
to
531365c
Compare
531365c
to
b2fcf09
Compare
b2fcf09
to
395980b
Compare
395980b
to
9bbab0f
Compare
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 only deletes the known_hosts entry on minikube delete --all
we should also delete them for a non --all
delete as well.
@ComradeProgrammer plz take another look so we could merge this before the release in upcoming weeks :) |
/ok-to-test |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@ComradeProgrammer have you addressed the comments from steven ? can you plz take another look so we could fit in in the release |
55d2c6e
to
6184085
Compare
@spowelljr @medyagh updated |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ComradeProgrammer The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
6184085
to
2d65564
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
2d65564
to
baccf08
Compare
Co-authored-by: Steven Powell <44844360+spowelljr@users.noreply.github.com>
cmd/minikube/cmd/ssh-host.go
Outdated
// these keys can be removed properly | ||
_, cc := mustload.Partial(ClusterFlagValue()) | ||
knownHostPath := filepath.Join(localpath.MiniPath(), "machines", config.MachineName(*cc, *n), "known_host") | ||
if err := os.WriteFile(knownHostPath, []byte(keys), 0666); err != nil { |
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.
Any reason this needs to be 666
vs 644
?
kvm2 driver with docker runtime
Times for minikube start: 47.0s 48.0s 47.8s 51.3s 47.5s Times for minikube ingress: 76.0s 15.0s 14.5s 14.5s 15.0s docker driver with docker runtime
Times for minikube start: 23.6s 23.1s 21.0s 23.1s 20.4s Times for minikube ingress: 12.8s 12.8s 12.3s 13.3s 13.9s docker driver with containerd runtime
Times for minikube start: 22.3s 19.2s 19.2s 22.9s 22.9s Times for minikube ingress: 22.8s 23.3s 22.8s 22.8s 23.8s |
Here are the number of top 10 failed tests in each environments with lowest flake rate.
Besides the following environments also have failed tests:
To see the flake rates of all tests by environment, click here. |
we need to test it manually.... @ComradeProgrammer can we do a few Manual Scenarios and paste them here, on both linux and macos maybe? or even windows |
Co-authored-by: Steven Powell <44844360+spowelljr@users.noreply.github.com>
4d12e4b
to
c22893e
Compare
@ComradeProgrammer: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
FIX #16868
This PR remove the public key of the node from user's known_hosts file when executing
minikube delete --all
What it does:
minikube ssh-host --append-known
for a node, the inserted key is not only written to the known_hosts file, but also written to$MINIHOME/machines/{node name}/known_host
minikube delete --all
, it go through all the folders under this$MINIHOME/machines/
, and remove keys stored in each folder from known_hosts fileBefore
Nothing happens when minikube delete, and old items in known_hosts remain
After
In a minikube cluster with multiple nodes
execute
minikube ssh-host --append-known
for a nodewhen the public key appears in known_hosts file
it also appears in
$MINIHOME/machines/{node name}/known_host
now after running
minikube delete --all
, the deprecated public key in known_hosts file also disappears