Cloud Dual-Stack --node-ip Handling #3705
Comments
k8s-ci-robot
added
the
needs-sig
|
/sig network |
k8s-ci-robot
added
sig/network
thockin
moved this from New, not evaluated
to Evaluated, not committed (undecided whether we want to do this or not)
in SIG-Network KEPs
|
/label lead-opted-in @thockin - FYI ^^ |
k8s-ci-robot
added
the
lead-opted-in
|
Hello @danwinship @thockin 👋, Enhancements team here. Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
|
/stage alpha |
k8s-ci-robot
added
the
stage/alpha
|
Thanks @danwinship, with all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀 The status of this enhancement is marked as |
thockin
moved this from Evaluated, not committed (undecided whether we want to do this or not)
to Pre-Alpha (we want to do this but the KEP or code is not merged yet)
in SIG-Network KEPs
|
Hi @danwinship 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release. Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release. |
|
Hey again @danwinship 👋 Enhancements team here, Here's where this enhancement currently stands:
Also please let me know if there are other PRs in k/k we should be tracking for this KEP. |
|
Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release. If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md /milestone clear |
|
@marosset: Those labels are not set on the issue: 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/test-infra repository. |
k8s-ci-robot
added
the
tracked/no
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
In order to allow passing dual-stack IPs to the `--node-ip` when using cloud provider, we need to pass the CloudDualStackNodeIPs feature gate. In order to do so properly, we are passing all known feature gates together with their respective configurations directly to the deployments of vSphere and OpenStack cloud providers. The CloudDualStackNodeIPs feature gate will only affect setups with 2 IP addresses as `--node-ip` together with `--cloud-provider`. Before K8s 1.27 this was not possible (you can either have dual-stack Node IPs or use a cloud provider, but not both). Upstream KEP kubernetes/enhancements#3705 adds ability to pass exactly 2 IPs as `--node-ip` also when using cloud provider, but given its alpha stage, feature gate is required here. Relates-to: OPNET-13 Relates-to: OPNET-230 Fixes: OPNET-319
|
/assign |
|
this targets beta: /stage beta |
k8s-ci-robot
added
stage/beta
|
Hello @danwinship, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancement and make sure the |
thockin
added
the
lead-opted-in
|
Hello @danwinship 👋, v1.29 Enhancements team here. Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀 The status of this enhancement is marked as |
|
Hi @danwinship 👋, v1.29 Docs Shadow here |
|
@harshitasao The only docs work needed was kubernetes/website#42875 which has merged since the last time I looked at this enhancement. I updated the checklist to reflect that. |
|
Hey again @danwinship 👋 v1.29 Enhancements team here, Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023 . Here's where this enhancement currently stands:
This KEP is Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks! |
|
Hi @danwinship ! 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release. If so, you need to open a PR placeholder in the website repository. |
Enhancement Description
One-line enhancement description (can be used as a release note): Synchronize
--node-ipbehavior between cloud-provider and non-cloud-provider clusters, to improve dual-stack behavior in clouds.Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3705-cloud-node-ips
Discussion Link: For dual stack deployments, node addresses show only one IP if node-ip parameter is passed kubernetes#111695 (comment) (and following comments), KEP-1664: Better Support for Dual-Stack Node Addresses #1665
Primary contact (assignee): @danwinship
Responsible SIGs: sig-network, with help from sig-node and sig-cloud-provider
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements) update PR(s):k/k) update PR(s):k/website) update PR(s):Beta
k/enhancements) update PR(s):k/k) update PR(s):k/website) update(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: