-
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
Promote IPv4/IPv6 dual-stack support to Beta #26826
Conversation
Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 99e46a5 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/6041fedebae4d60007706433 |
cc @reylejano |
/retitle Promote IPv4/IPv6 dual-stack support to Beta Please also update table on the page |
Clarifying how to disable the dual-stack feature when necessary. Co-authored-by: Qiming Teng <tengqm@outlook.com>
Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
Thanks, @tengqm!
I updated that table per your request, and also updated the other indicator on the top of the docs page so it is also correct for 1.21. |
lgtm EDIT just FYI, if we want to add a link to the kubeadm docs too |
Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
Hi, @aojea - I see that PR; I assumed it would be merged on its own - is there any action for me to take here in terms of edits to this Pr? Thanks. |
I'm not familiar with the website, so I don't know if we use cross references, so I just wanted to let you know, nothing else :) |
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 this PR.
The Markdown looks good to me.
I would however revise the text “If you enable IPv4/IPv6 dual-stack networking for your Kubernetes cluster, the cluster will support the simultaneous assignment of both IPv4 and IPv6 addresses.” in https://kubernetes.io/docs/concepts/services-networking/dual-stack/ - to reflect that you typically don't have to take any action to enable it.
You might also want to reword:
Enabling IPv4/IPv6 dual-stack on your Kubernetes cluster provides the following features:
|
||
{{< note >}} | ||
An example of an IPv4 CIDR: `10.244.0.0/16` (though you would supply your own address range) | ||
|
||
An example of an IPv6 CIDR: `fdXY:IJKL:MNOP:15::/64` (this shows the format but is not a valid address - see [RFC 4193](https://tools.ietf.org/html/rfc4193)) | ||
|
||
Starting in 1.21, IPv4/IPv6 dual-stack defaults to true. |
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.
Starting in 1.21, IPv4/IPv6 dual-stack defaults to true. | |
Starting in 1.21, IPv4/IPv6 dual-stack defaults to enabled. |
|
||
To enable IPv4/IPv6 dual-stack, enable the `IPv6DualStack` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for the relevant components of your cluster, and set dual-stack cluster network assignments: | ||
To configure IPv4/IPv6 dual-stack, set dual-stack cluster network assignments: |
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.
When features are beta, we typically still mention that the feature gate needs to be enabled, but tweak the wording. This helps people who are using older versions of Kubernetes spot that they might want to swap to reading documentation appropriate for their version.
Signed-off-by: Bridget Kromhout <bridget@kromhout.org>
Thanks for the review, @sftim! I've edited to reflect your feedback. |
/sig network |
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.
Markdown LGTM
@kubernetes/sig-network-pr-reviews any concerns?
LGTM |
/lgtm |
LGTM label has been added. Git tree hash: 8b7642859ccb456962f00b9468e4135a16876bfc
|
/assign @ChandaniM123 |
Hi, @sftim - thanks for giving an LGTM. I see @ChandaniM123 was assigned 3 days ago but I'm not sure what the next step is to get us the |
SIG Docs uses slightly different approval conventions from other SIGs, mostly I think because a merge to master is an update to the live website. |
I'm sure we'll get this fully reviewed well before the release. The deadline for docs to be reviewable is 2021-03-24 so you're getting this in nice and early @bridgetkromhout |
Hi @bridgetkromhout, thanks for following up! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: annajung 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 |
Enhancements issue: kubernetes/enhancements#563
Kubernetes PR: kubernetes/kubernetes#98969
Signed-off-by: Bridget Kromhout bridget@kromhout.org