-
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
Exclude by default address flag fix #1234 #71973
Conversation
Hi @MalloZup. 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. |
@kubernetes/sig-cluster-lifecycle-pr-reviews @MalloZup some k8s PRs need a "release note" to be added in the PR description. just add this:Does this PR introduce a user-facing change?:
|
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.
/ok-to-test
/retest |
@MalloZup it has to be in a code block using "```release-note" |
@neolit123 many thanks for your comments/helps ❤️ . Is the description now correct ? thank you |
not quite yet :) as you can see the bot has not removed the " ```release-note " instead of: " ``` " |
/retest |
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.
Thanks @MalloZup ! Finally we confine insecure listeners to history!
/lgtm
/retest |
/test pull-kubernetes-godeps |
seems ok now. flakyness in the tests has gone |
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
Not an urgent one, but it would be great to merge this simple fix this year. |
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.
@MalloZup Thanks for this PR! It is always nice to see new contributors start helping on kubeadm!
I'm ok with the change with only a minor concern that I want to double check with @luxas or @timothysc.
By removing --address=127.0.0.1
we are moving to use --bind-address
dafult that is 0.0.0.0
. That's means that we will expose the scheduler and the controller-manager secure port to the outside world. Is that ok for everyone?
/lgtm
I let final approval pending for the above check
@fabriziopandini thank you for feedback. if i can help here let me know. I hope one day to become a well-known old one contributor in the club 👵 😄 |
this is my concern exactly. we should do @MalloZup
|
/hold |
@neolit123 @fabriziopandini i have Feel free to take a look once you have some time. tia 🌻 |
@MalloZup thanks for this new version |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini, MalloZup 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.
/lgtm
thanks
/hold cancel |
What type of PR is this?
Does this PR introduce a user-facing change?
kubeadm: remove the deprecated "--address" flag for controller-manager and scheduler.
Which issue(s) this PR fixes:
fix kubernetes/kubeadm#1234
release note