Skip to content
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

Graduate IPv6 support to beta #1138

Closed
aojea opened this issue Jul 14, 2019 · 8 comments
Closed

Graduate IPv6 support to beta #1138

aojea opened this issue Jul 14, 2019 · 8 comments
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@aojea
Copy link
Member

aojea commented Jul 14, 2019

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) TODO

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

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jul 14, 2019

@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.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jul 14, 2019
@aojea
Copy link
Member Author

aojea commented Jul 14, 2019

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

@k8s-ci-robot k8s-ci-robot added the stage/beta Denotes an issue tracking an enhancement targeted for Beta status label Jul 14, 2019
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jul 14, 2019

@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 mariantalla added sig/network Categorizes an issue or PR as relevant to SIG Network. tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jul 15, 2019
@mariantalla mariantalla added this to the v1.16 milestone Jul 15, 2019
@mariantalla
Copy link
Contributor

mariantalla commented Jul 29, 2019

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
Copy link
Member

kacole2 commented Jul 29, 2019

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

@aojea
Copy link
Member Author

aojea commented Jul 29, 2019

@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
Copy link
Member

kacole2 commented Jul 29, 2019

@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 k8s-ci-robot removed this from the v1.16 milestone Jul 29, 2019
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Jul 29, 2019

@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.

@kacole2 kacole2 added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jul 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

No branches or pull requests

4 participants