IPv6 only support

[aojea]

Enhancement Description

• One-line enhancement description (can be used as a release note): Graduate IPv6 support to beta
• Kubernetes Enhancement Proposal: (link to kubernetes/enhancements file, if none yet, link to PR)
  Graduate IPv6 support to beta #1139
• Primary contact (assignee): @aojea
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y) 1.9
  • Beta release target (x.y) 1.16
  • Stable release target (x.y) 1.23

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

[k8s-ci-robot]

@aojea: There are no sig labels on this issue. Please add a sig label.

A sig label can be added by either:

1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
   e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

2. specifying the label manually: /sig <group-name>
   e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

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.

[aojea]

/sig-network
/stage beta
/milestone v1.16
/cc @lachie83 @thockin

[k8s-ci-robot]

@aojea: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/sig-network
/stage beta
/milestone v1.16
/cc @lachie83 @thockin

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.

[mariantalla]

Hey @aojea - just a quick reminder that this enhancement is currently at risk as its KEP hasn't merged yet (enhancements freeze is tomorrow).

[kacole2]

@aojea is this related to #508? If so, I believe we should close this and track it in that issue.

[aojea]

@aojea is this related to #508? If so, I believe we should close this and track it in that issue.

@kacole2 indeed is related, Im not very familiar with the process and opened a new one just for beta, feel free to close this so we can track everything in one issue only

[kacole2]

@aojea perfect. Please comment in #508 with your PR for the KEP and we will be good to go. Thanks for responding back

/milestone clear
/close

[k8s-ci-robot]

@kacole2: Closing this issue.

In response to this:

@aojea perfect. Please comment in #508 with your PR for the KEP and we will be good to go. Thanks for responding back

/milestone clear
/close

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.