-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add e2e-node test job for alpha features #7030
Conversation
/approve |
/cc @yujuhong |
Since this is an alpha feature, we probably don't want to enable it by default in the major kubelet e2e tests. |
@yujuhong SGTM @krzyzacy if I create a new job in this file, will it automatically be run? Is this readme still accurate that I need to create the job in two places? (if not I will update the readme) |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Add node-e2e test for ShareProcessNamespace **What this PR does / why we need it**: Adds a node-e2e test for kubernetes/enhancements#495 **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes #59554 **Special notes for your reviewer**: This requires a feature gate to be enabled in both the kubelet and API server. I'm not sure which jenkins configs need to be updated (or if these are even still used) so I just updated a pile of them. opened kubernetes/test-infra#7030 for https://github.com/kubernetes/test-infra/blob/master/jobs/config.json **Release note**: ```release-note NONE ```
@yujuhong I updated this to include a test for alpha features. Rather than constraining to tests marked alpha, it runs all of the (non-serial) tests since it's useful to know if an alpha feature breaks other tests or even if a stable change breaks an alpha feature. The PTAL. |
Hrmm, the test failed because I didn't add it to any dashboards in testgrid. I'm not exactly sure where it should go, so I'll hold off on this until I get feedback on the approach. |
@verb basically follow https://github.com/kubernetes/test-infra#create-a-new-job, testgrid config goes to https://github.com/kubernetes/test-infra/blob/master/testgrid/config.yaml |
/assign |
@yujuhong suggested placing this on the sig-node dashboard, so I've added it to the existing sig-node-kubelet. Tests are passing now. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: krzyzacy, verb 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 |
@verb: Updated the config configmap 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. |
This feature gate is required for test added in kubernetes/kubernetes#60509. I'm not sure which jobs should be updated, so I guessed.
/area jobs
/sig node