-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
feat(source): optional expose of nodes internal ipv6 #5192
feat(source): optional expose of nodes internal ipv6 #5192
Conversation
Hi @hjoshi123. Thanks for your PR. I'm waiting for a kubernetes-sigs 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-sigs/prow repository. |
Will update the documentation soon. Raising PR for visibility. |
/ok-to-test |
Thanks @hjoshi123 ! |
Could you add a warning message with the tests, to inform users that in follow-up release we are going to flip the flag/behaviour? |
The Warning message is missing, with description that if users would like to expose private Node IPs, they should configure the flag explicitly. Otherwise with next release, when we flip the flag, With explicit test, we have a helper for that external-dns/internal/testutils/log.go Line 36 in ecd57c8
|
/retest |
source/node_test.go
Outdated
require.NoError(t, err) | ||
|
||
if tc.exposeInternalIPv6 { | ||
buf := testutils.LogsToBuffer(log.DebugLevel, t) |
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 be log.WarningLevel
https://sematext.com/blog/logging-levels/
WARNING is not required as well, as
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.
yup will change that
This PR LGTM. |
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.
I request to change the behavior back to the original one, when adding the feature flag - I added my suggestion(s).
Sorry for some nits I added. If they are invalid or unnecessary, please let me know.
@jonasbadstuebner: changing LGTM is restricted to collaborators In response to this:
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. |
Thank you @hjoshi123, for taking the time to open this PR, it's greatly appreciated from my side! Even if I added a lot of comments, they are not meant to devalue your work! |
@jonasbadstuebner: changing LGTM is restricted to collaborators In response to this: 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. |
All good from my side, will approve when other comments resolved |
It's good to go from my side 🚀 Thank you again, @hjoshi123! |
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
/approve |
Ah I misunderstood - I thought I have to approve because there are pending requests by me shown. |
Everything ls correct. Thanks for reviewing. We review & approve. |
@jonasbadstuebner I'm unsure, maybe you will need to approve from Git Hub review tab, in order to remove the requested change. I'll try and we'll see :) /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ivankatliarchuk, jonasbadstuebner, mloiseleur 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 |
Description
This PR introduces a flag
expose-internal-ipv6
according to the proposal IPv6 proposal which states that we are going to implement a flag to allow users to determine if they want to expose their internal IPv6. For the next release, this flag is going to be defaulted as true which means internal IPv6s are exposed (this is how we treat IPv6s currently too). The next minor release will flip the flag and still provide users the option to go back if needed.Relates #4566
Related pull request #4574
Implement proposal IPv6 proposal
Checklist