-
Notifications
You must be signed in to change notification settings - Fork 14.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
Kubeadm/dual stack support in 1.21 #26675
Conversation
Deploy preview for kubernetes-io-master-staging ready! Built with commit acc69af https://deploy-preview-26675--kubernetes-io-master-staging.netlify.app |
2973d6d
to
a6c63a8
Compare
a6c63a8
to
6e3798c
Compare
6e3798c
to
774b910
Compare
Need I add a sample configuration file like? |
823be4f
to
acd337e
Compare
/cc i think including an example config is fine, v1beta2 is not deprecated and will be around for at least one more year (if not more). EDIT:
|
73a4089
to
1834a72
Compare
Updated the PR
|
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.
seems fine to me, not sure if this should be the page where we add it.
most importantly the PR should be against k/website's dev-1.21 branch.
the "change branch" option of github usually fails for k/website.
you can try:
- change the PR branch here
- do
git diff ... > patch.diff
locally to store the diff - delete local branch
- create a branch with same name based on
dev-1.21
locally - apply the patch
- push to the remote
@ sig-docs / @ sig -network do you think that we should have this guide in the kubeadm docs and just cross link to it from the sig network dual-stack page? |
d164a34
to
e5b3758
Compare
LGTM label has been added. Git tree hash: 1e5305e96882ef34642bb7d10f120933b0089394
|
LGTM |
/assign @jimangel |
/cc @sftim |
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 for proposing this new page.
- I'd prefer not to recommend using
fd00::/8
as this range is already deprecated. Let's use an IPv6 documentation IPv6 range instead. I added an example inline. - If it's feasible, lets use port 443 as the HTTPS port. This matches typical port assignments on the wider internet.
- I'm not sure why this page recommends setting
fail-swap-on
tofalse
.
kind: InitConfiguration | ||
localAPIEndpoint: | ||
advertiseAddress: "10.100.0.1" | ||
bindPort: 6443 |
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.
In documentation, I recommend using the https
port:
bindPort: 6443 | |
bindPort: 443 |
Port 443 is more recognisable to readers.
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 don't object to this, but for kubeadm users are more used to 6443, because that is the default.
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.
So I will keep it as 6443 or remove it ?
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.
my vote is to leave it 6443.
kubeadm init --feature-gates IPv6DualStack=false | ||
``` | ||
|
||
To make things more clear, here is an example kubeadm [configuration file](https://pkg.go.dev/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2) `kubeadm-config.yml` for the single-stack control plane node. |
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.
Depending on how thorough we want to be, it might be useful to point out that single-stack IPv6 is also supported.
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.
+1, emphasizing that is a good idea.
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.
Enabling the dual-stack feature doesn't mean that you need to use dual-stack addressing.
You can deploy a single-stack cluster that has the dual-stack networking feature enabled.
Current description. Need I add more?
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.
yes, seems good.
@@ -0,0 +1,144 @@ | |||
--- | |||
title: Dual-stack support with kubeadm |
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.
The improvement is dual stack support, but once that lands it's just “dual stack” (think about the page about RBAC; once it was new, but the page about it doesn't talk about RBAC support, just about RBAC).
How about:
title: Dual-stack support with kubeadm | |
title: Enable dual-stack networking using kubeadm |
?
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.
@neolit123 Do you agree to change the title?
Dual-stack support with kubeadm
is simple.
I prefer Enable dual-stack networking using kubeadm
as Tim says. The page mainly tells about how to enable it.
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 don't object.
content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
Show resolved
Hide resolved
content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
Outdated
Show resolved
Hide resolved
content/en/docs/setup/production-environment/tools/kubeadm/dual-stack-support.md
Outdated
Show resolved
Hide resolved
de85ed8
to
08064f5
Compare
@sftim Thanks for your reveiw. |
08064f5
to
945010f
Compare
/lgtm |
LGTM label has been added. Git tree hash: ba9c2264fad1a177a0325665019ad454a2d4cde2
|
Hi @pacoxu , this PR has a tech lgtm and updates addressing comments from a sig docs reviewer. Also wanted to share upcoming doc related dates for the 1.21 release:
|
@pacoxu Can you squash your commits Thank you |
Signed-off-by: pacoxu <paco.xu@daocloud.io> Co-authored-by: Lubomir I. Ivanov <neolit123@gmail.com> Co-authored-by: Tim Bannister <tim@scalefactory.com>
945010f
to
5a6c424
Compare
@reylejano updated. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm 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 |
part of kubernetes/kubeadm#1612
https://kubernetes.io/docs/concepts/services-networking/dual-stack/
kubeadm dual-stack install log: https://gist.github.com/pacoxu/3fda7ccbccca82a0cd791cad454ae69f