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
kubeadm: a warning to user as ipv6 site-local is deprecated #99574
kubeadm: a warning to user as ipv6 site-local is deprecated #99574
Conversation
@pacoxu: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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 don't know if we should do this, it doesn't look as a deprecation to me, is that basically those addresses will not work due to their properties. |
Maybe we should forbid the use of those subnets here. Site-Local address is something very weird (which seems to be right but cannot be shown in kubernetes cluster with docker). IPV6
IPV4
|
yeah, my point is to what point you want to be opinionated, if you read those ip addresses definition you know that you shouldn't use it ... |
To explain something more, I agree with you that users should know that and don't use those subnets as common sense. However, I worked on some projects that the user may challenge that this is not raising during installation.
|
history of my life :) |
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.
@pacoxu
i suggested some minor changes.
also release note should be:
kubeadm: warn when a user provided subnet is in site-local range - i.e. contains addresses that belong to FEC0::/10
@aojea @pacoxu
having this warning doesn't seem to hurt much.
but i tend to agree that maybe users should read the specs and understand they should not use a certain range, instead of kubeadm warning them.
@aojea leaving LGTM to you.
fe0b0c4
to
2dbff4a
Compare
/test pull-kubernetes-node-e2e |
2dbff4a
to
154cd74
Compare
/lgtm |
2920488
to
1e89c85
Compare
/lgtm |
1e89c85
to
5636e37
Compare
rebase to latest master |
/lgtm |
…e deprecated Signed-off-by: pacoxu <paco.xu@daocloud.io> Co-authored-by: Antonio Ojea <antonio.ojea.garcia@gmail.com> Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com>
5636e37
to
3c33cea
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.
/lgtm
/approve
/hold cancel
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123, pacoxu 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 |
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/sig network
/kind feature
/cc @aojea
What this PR does / why we need it:
Site local addresses are the ones that belong to the range FEC0::/10 and are deprecated
As it is deprecated, we may disallow this subnet or give a warning when the user uses this subnet.
Or it would be a error.
Which issue(s) this PR fixes:
same as #91935
Special notes for your reviewer:
See details in #89251 (comment)
http://linux-ip.net/html/tools-ip-address.html
Site-local addresses are supposed to be used within a site. Routers will not forward any packet with site-local source or destination address outside the site.
https://tools.ietf.org/html/rfc3879
deprecated in 2004
Does this PR introduce a user-facing change?