-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
KEP-4369: promote RelaxedEnvironmentVariableValidation feature gate to beta #126897
KEP-4369: promote RelaxedEnvironmentVariableValidation feature gate to beta #126897
Conversation
/hold Please update the KEP first before merging it. |
3ba95c9
to
eaa24f6
Compare
eaa24f6
to
0a04e94
Compare
/remove-sig api-machinery |
We added the following tests during the alpha phase. As the feature gate is enabled by default, they will be executed in e2e tests. kubernetes/test/e2e/common/node/expansion.go Lines 376 to 411 in 0daa75b
kubernetes/test/e2e/common/node/configmap.go Lines 247 to 294 in 0daa75b
kubernetes/test/e2e/common/node/secrets.go Lines 243 to 290 in 0daa75b
|
Thank you! Please link to a job run in our CI that is testing this and then I'll be fine with merging this. |
/test |
@kannon92: The
The following commands are available to trigger optional jobs:
Use
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-sigs/prow repository. |
/test pull-kubernetes-e2e-kind-beta-features |
No, they won't, because of the |
Thanks for the heads up, that |
Have you confirmed that these tests are in that job? |
I checked the results of I had thought that the environment variables in
|
@HirazawaUi: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
As I said, We are working towards allowing testing of simple features in those shared alpha/beta jobs, but we are not there yet. Even if that hard worked already, it would have been your responsibility as feature owner to verify that your feature is really being tested. |
I'm sorry, I'm not very familiar with this area. Based on my recent investigation, it seems that I need to open a PR to https://github.com/kubernetes/test-infra to add tests for RelaxedEnvironmentVariableValidation, is that correct? |
Yes. That is correct. Let's try adding a presubmit first and make sure that works. Once that is verified, then we can add a periodic so that this test runs periodically. |
PR has been opened |
/test |
@HirazawaUi: The
The following commands are available to trigger optional jobs:
Use
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-sigs/prow repository. |
/test |
@HirazawaUi: The
The following commands are available to trigger optional jobs:
Use
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-sigs/prow repository. |
/test pull-kubernetes-e2e-relaxed-environment-variable-validation |
/lgtm Can you add a periodic job for this also? |
LGTM label has been added. Git tree hash: ccde002b9bedd73cb634d6942dd394a1c2aef3d8
|
Once the periodic job is up, I think this should go in. I just want to make sure we have coverage on this feature before we promote to beta. We have a presubmit but having a periodic can help deduce regressions. |
KEP kubernetes/enhancements#4805 was merged. Feel free to unhold once this is ready. |
@HirazawaUi has opened up the periodic job. /hold cancel |
What type of PR is this?
/kind feature
What this PR does / why we need it:
According to the KEP, we promote it to beta in version 1.32.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: