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
move IPv6DualStack feature to stable. #104691
Conversation
Enhancement issue: kubernetes/enhancements#563 |
cc9cfc7
to
d2f6c29
Compare
cmd/kubeadm/app/apis/output/v1alpha1/zz_generated.conversion.go
Outdated
Show resolved
Hide resolved
ed32ad6
to
f63f814
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.
Thanks!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: khenidak, thockin 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 |
/triage accepted |
* kube-proxy * endpoints controller * app: kube-controller-manager * app: cloud-controller-manager * kubelet * app: api-server * node utils + registry/strategy * api: validation (comment removal) * api:pod strategy (util pkg) * api: docs * core: integration testing * kubeadm: change feature gate to GA * service registry and rest stack * move feature to GA * generated
What type of PR is this?
/kind feature
What this PR does / why we need it:
moves dual-stack feature to stable by removing conditional checks against feature flags and modify the code as needed.
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
We have an interesting problem in kube-proxy init logic where it does not fail if it does not find iptables support for IPv6. And it does not check if iptables support is enabled even for IPv6 single cluster. I have a couple of ideas around this. will include later in the same PR. I left a note in the code.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: