-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Remove docker node periodics, ensure CRI replacements #24595
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
Conversation
86cfe31 to
fbe6e99
Compare
d3148be to
9045cd8
Compare
95b6ecd to
f779bba
Compare
eff0fe2 to
848cb15
Compare
848cb15 to
7074300
Compare
|
Tests pass, ready for review. |
d5c7824 to
1722302
Compare
Coverage for this is provided by ci-containerd-node-e2e and ci-crio-cgroupv1-node-e2e-conformance.
Covered by ci-cri-containerd-e2e-cos-gce-alpha-features and new cri-o job ci-crio-cgroupv1-node-e2e-alpha.
Replace with ci-kubernetes-node-kubelet-containerd-eviction and ci-crio-cgroupv1-node-e2e-eviction.
Covered by ci-cri-containerd-node-e2e-features and ci-crio-cgroupv1-node-e2e-features.
Covered by ci-cri-containerd-e2e-cos-gce-flaky and ci-crio-cgroupv1-node-e2e-flaky.
| annotations: | ||
| testgrid-dashboards: sig-node-containerd | ||
| testgrid-tab-name: node-e2e-features | ||
| - name: ci-cri-containerd-node-e2e-unlabelled |
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.
why renaming from orphans?
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.
Because it's a pretty insensitive name; new name is more descriptive and inclusive.
It's running on docker, and it's also running no tests. I'm just removing it for now.
Replace it with new jobs ci-cri-containerd-node-e2e-unlabelled and ci-crio-cgroupv1-node-e2e-unlabelled which have more descriptive names.
These are covered by ci-kubernetes-node-kubelet-serial-containerd and ci-kubernetes-node-kubelet-serial-cri-o jobs. DevicePluginProbe tests should be readded in a follow-up; they are currently failing. See kubernetes/kubernetes#106635
| testgrid-tab-name: ci-crio-cgroupv1-node-e2e-conformance | ||
| testgrid-alert-email: [email protected] | ||
| description: "OWNER: sig-node; runs NodeConformance e2e tests with crio master and cgroup v1" | ||
| - name: ci-crio-cgroupv1-node-e2e-alpha |
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.
is it a new test or I am missing some renaming? no objections, just trying to understand
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.
maybe doing as a separate PR would be easier to review
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.
New test to add 2 container runtimes of coverage for alpha features. Explained in each commit comment which jobs were replacing each removal. Added jobs in containerd config are similar.
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.
maybe doing as a separate PR would be easier to review
you may want to review commit by commit, that's why I split it up that way
I will file follow-up issues for those and alert the owners.
1722302 to
4aa39f6
Compare
| - --test-args=--kubelet-flags="--cgroups-per-qos=true --cgroup-root=/" | ||
| - --image-config-file=/home/prow/go/src/k8s.io/test-infra/jobs/e2e_node/image-config.yaml | ||
|
|
||
| - name: ci-kubernetes-node-kubelet-alpha |
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.
is the
| name: ci-cri-containerd-e2e-cos-gce-alpha-features |
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.
From 26adeb7 commit message:
Remove ci-kubernetes-node-kubelet-alpha/-kubetest2
Covered by ci-cri-containerd-e2e-cos-gce-alpha-features and new cri-o
job ci-crio-cgroupv1-node-e2e-alpha.
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, ehashman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| testgrid-tab-name: ci-crio-cgroupv1-node-e2e-features | ||
| testgrid-alert-email: [email protected] | ||
| description: "OWNER: sig-node; runs NodeFeatures e2e tests with crio master and cgroup v1" | ||
| - name: ci-crio-cgroupv1-node-e2e-eviction |
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 understand now that you are trying to add cri-o replacement for docker as well. Would it be better to have the names pattern match between runtimes?
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.
between ci-kubernetes-node-kubelet-containerd-eviction and ci-crio-cgroupv1-node-e2e-eviction, can we match the name pattern or cross reference tests?
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.
Can we rename in a separate PR? All of the job names are kind of out of sync and I know SIG Testing had previously suggested we take the runtimes out of the job names entirely.
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.
/lgtm
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.
|
/retest-required looks unrelated, maybe a flake? |
|
@ehashman: Updated the
DetailsIn 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. |
Going through tab by tab on node-kubelet-serial
It is a mistake to try to do the presubmits in the same PR, let's do that separately.
Follow-ups:
/sig node
Fixes #24592