Skip to content

k8s recovery tests: Bump kindest/node to v1.33.1#32710

Merged
def- merged 1 commit into
MaterializeInc:mainfrom
def-:pr-k8s-recovery
Jun 11, 2025
Merged

k8s recovery tests: Bump kindest/node to v1.33.1#32710
def- merged 1 commit into
MaterializeInc:mainfrom
def-:pr-k8s-recovery

Conversation

@def-

@def- def- commented Jun 11, 2025

Copy link
Copy Markdown
Contributor

Follow-up to #32694 Failures seen in https://buildkite.com/materialize/nightly/builds/12268#01975c36-7adf-4ace-9e81-67d43af9c4f8

this version of kubeadm only supports deploying clusters with the control plane version >= 1.32.0. Current version: v1.29.7

Test run: https://buildkite.com/materialize/nightly/builds/12271

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@def- def- force-pushed the pr-k8s-recovery branch from 83e0eb8 to 9a00f84 Compare June 11, 2025 08:43
@def- def- changed the title k8s recovery tests: Bump kindest/node to v1.31.6 k8s recovery tests: Bump kindest/node to v1.33.1 Jun 11, 2025
@def- def- requested a review from bobbyiliev June 11, 2025 09:04
@def- def- merged commit cae1b90 into MaterializeInc:main Jun 11, 2025
13 of 15 checks passed
@def- def- deleted the pr-k8s-recovery branch June 11, 2025 09:10
nodes:
- role: control-plane
image: kindest/node:v1.29.7
image: kindest/node:v1.33.1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

When setting the image, please set the image for all nodes in the cluster. It happens to work this time because 1.33 is the latest. The error message is also misleading, as it would work with 1.31.6 if all nodes had that image. You just can't mix nodes running images more than one minor version apart. It chooses a kubeadm based on the latest node image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants