Replies: 1 comment
-
This sort of stuff is all covered by Cluster API (or a competing standard like the talos API), and is not usually part of the distro itself. Rancher handles CAPI for K3s and RKE2, although it is not currently easy to use directly. There is a 3rd party standalone implementation under development at https://github.com/cluster-api-provider-k3s/cluster-api-k3s |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
Currently, management of k3s installation and maintenance is only possible on a local instance shell and it is static. This make "re-shaping" the cluster node configurations a tedious task, effectively making each k3s node a pet rather than cattle.
Describe the solution you'd like
It would be incredibly useful and powerful if k3s agent/worker role and configurations could be managed remotely. This could be enabled by implementing a subset of talos api such as upgrading, bootstrapping, resetting, discovery? etc and a management tool similar to talosctl. It could potentially allow k3s clusters to resize by adding nodes incrementally as needed similar to cluster autoscaler.
Describe alternatives you've considered
talos linux requires going all in including the host os itself which isn't feasible always.
Additional context
This inspired by talos linux
Beta Was this translation helpful? Give feedback.
All reactions