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
Dumb typo in kubeadm instructions #43022
Conversation
Signed-off-by: Joe Beda <joe.github@bedafamily.com>
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.
/lgtm
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED The following people have approved this PR: dmmcquay, jbeda Needs approval from an approver in each of these OWNERS Files:
We suggest the following people: |
@k8s-bot unit test this |
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.
Should we change the initial kubeadm init/join? warning as well to indicate the beta quality?
Idk what's beneficial here, because we'll still probably change the implementation in v1.7...
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
@k8s-bot kops aws e2e test this It's the route53 throttling we're dealing with right now; patch working its way through the queues concurrently. |
Automatic merge from submit-queue (batch tested with PRs 43022, 43078) |
@jbeda: The following test(s) failed:
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/test-infra repository. I understand the commands that are listed here. |
I typo'd chown as chmod in kubeadm instructions. Ugh.