-
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
Conversation
I have to add a section to include the ipv6 jobs at least as part of the presubmits and to the release to avoid situations like #80388 |
@dims let me add it to the KEP so it can be discussed in the reviews, I will try to finish it this week 😄 |
4cb2f23
to
8d625ce
Compare
f926d20
to
4be84c3
Compare
## 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 comment
The reason will be displayed to describe this comment to others. Learn more.
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 ...
## 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 comment
The 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)
## Proposal | ||
|
||
* Make kind IPv6 e2e jobs mandatory for all PRs | ||
* Create IPv6 e2e jobs on at least 2 Cloud Providers and publish the results on testgrid |
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.
IMHO this (2 cloud provider IPv6 jobs) is potentially a pretty significant hurdle.
You can't just create e2e jobs on a provider, you need credits from the provider and a working system to deploy IPv6 clusters on them besides the CI glue.
Today we have some AWS quota and lots of GCP quota, for which we have kops tooling on AWS and a few options on GCE, neither of which sets of (tools, provider) do IPv6 clusters AFAIK.
Is there a concrete plan for this particular point? Otherwise I suspect this will block progress.
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.
@BenTheElder we need to shop this around in the sig-cloudprovider and get volunteers to help
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.
the main reason for asking this is - since beta means it's on by default, if its on by default but does not work on most of the cloud providers, it's not really useful.
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.
Well, technically is on by default, you don't have to enable anything, you configure ipv6 address, it work in ipv6, you configure ipv4 address it works in ipv4.
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.
@aojea we don't have a feature flag? hmmm
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.
Right, I see that misunderstanding lately, this is not a feature as in typical software development. When you develop your application you usually don't care about the network protocol, what @leblancd and others implemented is that k8s will use ipv6 addresses instead of ipv4, you don't have to turn on anything,
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.
@aojea Ack thanks. I am ok with just one cloud provider in that case for beta.
|
||
* Make kind IPv6 e2e jobs mandatory for all PRs | ||
* Create IPv6 e2e jobs on at least 2 Cloud Providers and publish the results on testgrid | ||
* Move all IPv6 e2e conformance jobs (kind + Cloud Providers) into release blocking |
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.
(following the standard process to move things into blocking following proving that they are stable and contacting SIG-release of course)
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.
Ok, thanks, will reword and explain it better
cc @khenidak |
/assign @johnbelamaric @thockin |
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: aojea, 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 |
Graduate IPv6 support to beta, it was in alpha status since 1.9 and a CI system was added to avoid regressions and guarantee the quality
Ref: #1138