-
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
[KEP-3041] - remove node special feature and node alpha feature from test-infra for non release branch #33828
[KEP-3041] - remove node special feature and node alpha feature from test-infra for non release branch #33828
Conversation
/hold We should merge this once 1.33 opens up for development. |
b05916b
to
0e45a9a
Compare
0e45a9a
to
754f624
Compare
…r non release branch
754f624
to
fa5761f
Compare
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 for doing this as it is confusing me to me too.
@@ -227,7 +227,7 @@ periodics: | |||
- '--node-test-args=--container-runtime-endpoint=unix:///run/containerd/containerd.sock --container-runtime-process-name=containerd --container-runtime-pid-file= --kubelet-flags="--cgroups-per-qos=true --cgroup-root=/ --runtime-cgroups=/system.slice/containerd.service" --extra-log="{\"name\": \"containerd.log\", \"journalctl\": [\"-u\", \"containerd*\"]}"' | |||
- --node-tests=true | |||
- --provider=gce | |||
- --test_args=--nodes=1 --timeout=4h --focus="\[Serial\]" --skip="\[Flaky\]|\[Benchmark\]|\[NodeSpecialFeature:.+\]|\[NodeSpecialFeature\]|\[NodeAlphaFeature:.+\]|\[NodeAlphaFeature\]|\[NodeFeature:Eviction\]|\[NodeFeature:NodeSwap]" |
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.
Instead of removing, should we replace it with specific feature labels like Feature:PodLevelResource
and Feature:InPlacePodVerticalScaling
? This would allow us to exclude tests related to in-development features from certain jobs.
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.
During the sig-node CI meeting, we discussed a strategy to submit your 2 changes. This approach would streamline the PR submission process. By replacing the generic labels NodeAlphaFeature
and NodeSpecialFeature
with specific feature labels, we can prioritize the submission of this PR, followed by the k/k PR.
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.
That was about a different item. In this case, We are skipping based on NodeSpecialFeature. I think we can drop this as is.
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.
In this case I think merging the k8s PR first and then this one is sufficient..
/hold cancel |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kannon92, SergeyKanzhelev 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 |
@kannon92: Updated the
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. |
Address the test-infra part of #33823.