-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 #1139
Merged
+98
−0
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
Create 20190714-IPv6-beta-proposal.md
commit 6204729e062c5bb5a03d45ed1166d5cf38102359
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,94 @@ | ||
--- | ||
title: graduate-ipv6-to-beta | ||
authors: | ||
- "@aojea" | ||
owning-sig: sig-network | ||
participating-sigs: | ||
reviewers: | ||
- "@bentheelder" | ||
- "@andrewsykim" | ||
- "@khenidak" | ||
approvers: | ||
- "@lachie83" | ||
- "@thockin" | ||
editor: TBD | ||
creation-date: 2019-07-14 | ||
last-updated: 2019-07-23 | ||
status: implementable | ||
see-also: | ||
replaces: | ||
superseded-by: | ||
--- | ||
|
||
# Graduate IPv6 to beta | ||
|
||
## Table of Contents | ||
|
||
<!-- toc --> | ||
- [Summary](#summary) | ||
- [Motivation](#motivation) | ||
- [Goals](#goals) | ||
- [Non-Goals](#non-goals) | ||
- [User Stories](#user-stories) | ||
- [Proposal](#proposal) | ||
- [Design](#design) | ||
- [Test Plan](#test-plan) | ||
- [Needed Tests](#needed-tests) | ||
- [Graduation Criteria](#graduation-criteria) | ||
- [Implementation History](#implementation-history) | ||
<!-- /toc --> | ||
|
||
## Summary | ||
|
||
Support for IPv6-only clusters was added in Kubernetes 1.9 as an alpha feature, with version 1.13 the Kubernetes default DNS server changed to CoreDNS which has full IPv6 support, there are several CNI plugins with IPv6 support and Dual Stack support is being implemented during the 1.16 cycle. | ||
|
||
|
||
## Motivation | ||
|
||
IPv6 adoption is ramping up with the advances in IoT space and explosion in number of mobile devices, this adoption will continue to grow as we can observe at the Google IPv6 adoption statistics https://www.google.com/intl/en/ipv6/statistics.html. | ||
|
||
There are cloud providers that are starting to support IPv6 clusters, the dual stack implementation will facilitate the migration from IPv4 to IPv6 and CI testing was implemented using the kind project. | ||
|
||
Therefore, we would like to graduate IPv6 support from Alpha to Beta. | ||
|
||
### Goals | ||
|
||
* Promote IPv6 to beta version. | ||
|
||
### Non-Goals | ||
|
||
* IPv6 is NOT Dual-stack | ||
|
||
### User Stories | ||
|
||
* A user can deploy, operate and use a kubernetes cluster in an IPv6 only environment. | ||
|
||
## Proposal | ||
|
||
* Make kind IPv6 e2e jobs mandatory for all PRs | ||
* Have signal on IPv6 e2e jobs running in at least one Cloud Provider | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd request this to be changed to at least 2 cloud providers. please explicitly say that we need the results in the testgrid as well for the release team. ("signal" is not expressive enough i feel) |
||
|
||
## Design | ||
|
||
### Test Plan | ||
|
||
#### Needed Tests | ||
|
||
- Run a CI with conformance E2E tests on an IPv6 only kubernetes cluster. | ||
- Run a CI with conformance E2E tests on a cloud provider. | ||
|
||
### Graduation Criteria | ||
- [x] It has IPv4 feature parity | ||
- [x] It has CI | ||
- [x] It has passed all e2e conformance tests | ||
- [x] It is documented | ||
- [ ] It is being used at least by one Cloud Provider | ||
aojea marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
|
||
## Implementation History | ||
|
||
- [IPv6 Support was introduced as alpha in kubernetes 1.9](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.9.md) | ||
- [IPv6 Support enhancement request](https://github.com/kubernetes/enhancements/issues/508) | ||
- [IPv6 implementation tracking issue](https://github.com/kubernetes/kubernetes/issues/1443) | ||
- [IPv6 CI](https://testgrid.k8s.io/conformance-kind#kind%20(IPv6),%20master%20(dev)) | ||
- [Kind IPv6 support](https://github.com/kubernetes-sigs/kind/pull/636) |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@thockin @lachie83 is this feasible?
are those jobs available for all kubernetes members or are they only configured by the companies?
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.
anyone can publish conformance signal to testgrid, we already have a KEP for that.
anyone can also donate resources for their cloud to be used by prow / kubernetes's own CI
... we apparently even have EKS clusters on prow.k8s.io today.
however, the fact that someone could do this doesn't mean they will ...