Support building e2e Kind node images for Kubernetes patch releases#752
Support building e2e Kind node images for Kubernetes patch releases#752yankay wants to merge 1 commit intokubernetes-sigs:mainfrom
Conversation
✅ Deploy Preview for kubernetes-sigs-lws ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: yankay The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Pull request overview
This PR updates Kubernetes-related Go module dependencies to address failing tests when running against Kubernetes 1.35.
Changes:
- Bumps
sigs.k8s.io/controller-runtimefromv0.23.0tov0.23.1. - Bumps
sigs.k8s.io/structured-merge-diff/v6fromv6.3.1tov6.3.2-0.20260122202528-d9cc6641c482. - Updates
go.sumentries to align with the new dependency versions.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| go.mod | Updates controller-runtime and structured-merge-diff dependencies to newer versions compatible with Kubernetes 1.35. |
| go.sum | Synchronizes checksum entries with the updated dependency versions from go.mod. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
7c94439 to
58b849a
Compare
58b849a to
973f4e0
Compare
973f4e0 to
4ccdc11
Compare
4ccdc11 to
d06f3e6
Compare
|
/retest |
|
Updated the approach: instead of downgrading to Root cause: kubernetes/kubernetes#137409 — /retest |
0b5076f to
5066b8b
Compare
Lets e2e jobs build a Kubernetes patch-release Kind node image on demand before running tests, by adding a Makefile-driven kind-node-image-build target controlled via E2E_KIND_BUILD_NODE_IMAGE_VERSION. When E2E_KIND_BUILD_NODE_IMAGE_VERSION is unset, behavior is unchanged and the image referenced by E2E_KIND_VERSION is pulled as before. When set, the target invokes "kind build node-image <version> --image <E2E_KIND_VERSION>" only if the target image is not already present locally, which lets CI test against a patch release for which no kindest/node image has been published yet (for example v1.35.4, see kubernetes-sigs/kind#4131). This is wired into the existing test-e2e, test-e2e-cert-manager, test-e2e-gang-scheduling-volcano, and disaggregatedset/test-e2e targets, mirroring the on-demand build pattern used by Kueue. Part of kubernetes-sigs#751 Signed-off-by: Kay Yan <kay.yan@daocloud.io>
0351fc9 to
ae7025f
Compare
|
/retest |
|
@yankay: 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. DetailsInstructions 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. |
|
/test pull-lws-test-e2e-main-1-34 |
|
/test pull-lws-test-e2e-main-1-34 |
|
Hi @Edwinhr716, could you take a look when you have a chance? This unblocks e2e against the v1.35 StatefulSet |
|
Friendly ping @ahg-g @Edwinhr716 — could one of you take a look when you have a moment? All CI is green (1.32 / 1.33 / 1.34 e2e + integration + unit). This unblocks e2e against the upstream v1.35 StatefulSet Thanks! |
What type of PR is this?
/kind failing-test
What this PR does / why we need it
Adds a Makefile target and
E2E_KIND_BUILD_NODE_IMAGE_VERSIONknob so e2e jobs can build a Kind node image on demand viakind build node-image, mirroring Kueue's pattern.This is needed because the StatefulSet
Parallelregression in v1.35.0/v1.35.1 (kubernetes/kubernetes#137409) is fixed in v1.35.4, butkindest/node:v1.35.4is not published (kubernetes-sigs/kind#4131). When the new var is unset, behavior is unchanged.Which issue(s) this PR fixes
Part of #751
Special notes for your reviewer
Follow-up
kubernetes/test-infraPR can set lws Prow jobs to:```yaml
value: kindest/node:v1.35.4
value: v1.35.4
```
Validated with `make -n test-e2e` (root and `disaggregatedset`) and a local `kindest/node:v1.35.4` build.
Does this PR introduce a user-facing change?
```release-note
NONE
```