Skip to content
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

update docker rke2 template for fleet #22

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

salasberryfin
Copy link
Contributor

Description

Update Docker RKE2 template based on recent changes. This aligns the template with what's used in Turtles E2E. Additionally, this updates K8s version.

@salasberryfin salasberryfin requested review from a team and dharmit and removed request for dharmit February 10, 2025 15:45
Copy link
Contributor

@dharmit dharmit left a comment

Choose a reason for hiding this comment

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

Just a question.

@@ -41,7 +45,7 @@ metadata:
spec:
template:
spec:
customImage: kindest/node:v1.26.0
customImage: kindest/node:v1.31.0
Copy link
Contributor

Choose a reason for hiding this comment

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

We recommend 1.30.0 here: https://github.com/rancher/turtles/blob/8a1d7e68999a1cfc7888ac2cf4d802a85ca1a3f9/scripts/kind-cluster-with-extramounts.yaml.

In CAPRKE2 docs, we don't recommend any version, so it pulls 1.32.0 as that's presently the latest: https://github.com/rancher/cluster-api-provider-rke2/blob/c00d2a44600e43f0bef2dd85daabf04da607b213/docs/book/src/04_developer/01_development.md

And now here 1.31.0 across this file.

My point being, should we have a uniform k8s version being used across the places? From dev perspective, it's probably not important, but it is from users/customers POV, IMO.

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.

2 participants