Skip to content

Conversation

@cbarria
Copy link
Contributor

@cbarria cbarria commented Sep 30, 2025

  • Migrate to RKE2

@cbarria cbarria self-assigned this Sep 30, 2025
@cbarria cbarria added the enhancement New feature or request label Sep 30, 2025
@cbarria cbarria marked this pull request as ready for review September 30, 2025 20:42
@cbarria cbarria requested a review from a team September 30, 2025 20:43
Copy link
Contributor

@dtapiacl dtapiacl left a comment

Choose a reason for hiding this comment

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

LGTM.

dtapiacl
dtapiacl approved these changes Oct 2, 2025
Copy link
Contributor

@gseriche gseriche left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Contributor

@dtapiacl dtapiacl left a comment

Choose a reason for hiding this comment

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

  1. Question: Where is the network configuration for the cluster ?

Copy link
Member

@jhoblitt jhoblitt left a comment

Choose a reason for hiding this comment

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

For a 4 (or 5) node cluster, I think all nodes should be control plane. Now also seems like a good time to migrate nfs2.cp back to a lukay node.

As part of any baremetal k8s cluster rebuild, in the interested of reliability and consistency, the networking should be converted to use a bonded trunk with the fqdn IP on bridge interface -- even if there is only a single vlan on the trunk.

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

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants