docs: use an existing kindest/node tag in the k8s node image example - #2257
Merged
Conversation
egernst
approved these changes
Sep 11, 2026
Code Coverage
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of Change
Motivation and Context
kindest/node:v1.34.4does not exist on Docker Hub, so the example in docs/kubernetes.md fails with a 404 on the manifest. The 1.34 tags available are v1.34.0, .2, .3, .8 and .11. This switches the example to v1.34.11.Testing
container run docker.io/kindest/node:v1.34.4fails with404 Not Foundon the manifest;docker.io/kindest/node:v1.34.11pulls and boots.