Skip to content

Conversation

pohly
Copy link
Contributor

@pohly pohly commented Aug 29, 2025

This includes several different changes, see individual commits.

Replaces #35225

/assign @bart0sh
/cc @ffromani @Jpsassine

pohly added 4 commits August 29, 2025 15:25
This currently covers skew testing between 1.32 and 1.35.
The node jobs incorrectly used OffByDefault, without actually enabling all
off-by-default feature gates. This caused ResourceHealthStatus test to run and
fail until that feature gate was explicitly excluded. We don't want to repeat
that for every new alpha feature; updating the allow list (= isSubsetOf) is the
right approach.

Adding a job which includes alpha and beta features follows in a separate commit.
Several reasons:
- Testing primarily with cgroup v1 doesn't make sense, it's not recommended anymore.
- containerd jobs seem to be slightly faster.
- crio image config updates caused job failures a few times.
In contrast to the kind-dra-all job, the new node job enables all feature
gates. This is a bit simpler, with the only drawback (for us as DRA developers)
that some other alpha or beta feature might cause test failures in DRA
tests. For Kubernetes it's good to catch that. The new job is conceptually
similar to ci-kubernetes-kind-alpha-beta-features and is names similarly.

The new job is not release informing because of the alpha features.
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/config Issues or PRs related to code in /config area/jobs size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. sig/node Categorizes an issue or PR as relevant to SIG Node. labels Aug 29, 2025
@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Aug 29, 2025
# This job runs the current e2e.test against a cluster where the kubelet is from the "current - 3" release.
#
# It enables and tests the same features as kind-dra.
[kind-dra-n-3]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to test this new job on canary first?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's optional. The effect of getting it wrong is therefore minor and the risk is low (we ran the same configuration a short while ago, before they bumped the master version). I think it's fine without doing a canary first.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 30, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bart0sh, pohly

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 30, 2025
@k8s-ci-robot k8s-ci-robot merged commit 3c02076 into kubernetes:master Aug 30, 2025
7 checks passed
@k8s-ci-robot
Copy link
Contributor

@pohly: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

  • key dra-canary.yaml using file config/jobs/kubernetes/sig-node/dra-canary.yaml
  • key dra-ci.yaml using file config/jobs/kubernetes/sig-node/dra-ci.yaml
  • key dra-presubmit.yaml using file config/jobs/kubernetes/sig-node/dra-presubmit.yaml

In response to this:

This includes several different changes, see individual commits.

Replaces #35225

/assign @bart0sh
/cc @ffromani @Jpsassine

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.

@github-project-automation github-project-automation bot moved this from Triage to Done in SIG Node CI/Test Board Aug 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/jobs cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
Development

Successfully merging this pull request may close these issues.

3 participants