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
bump IPv6DualStack to beta (early merge from 1.21) #618
Conversation
…d (beta: gate is always on)
@danwinship: the contents of this pull request could be automatically validated. The following commits are valid:
|
/retest |
2 similar comments
/retest |
/retest |
/test e2e-gcp-upgrade |
e2e-gcp-upgrade is failing for everyone since Thursday |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: aojea, danwinship The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
2 similar comments
/retest |
/retest |
@danwinship: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/assign @soltysh this is just an early merge from 1.21 to simplify our 4.8 dual-stack testing |
Spoke with @danwinship on slack, this can wait roughly a week, by then we should be ready with #624. |
@soltysh: Closed this PR. 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. |
Pull in the IPv6DualStack alpha->beta migration now, so we can test dual stack in master without needing to override feature gates.
I skimmed for other post-1.20 dual-stack related commits and found:
none of which seems immediately necessary (though we may end up merging a few more bits before the eventual 1.21 rebase...)
cc @aojea