`etcd`-taint on rancher-provided clusters

[max06]

Good morning,

I recently ran into some smaller issues with rancher-provided elemental-clusters, related to the roles rancher sets for the node-pools.

See this example:

The node-pool shown (ignore the checked worker-role) causes assigned nodes to get NoExecute-taints for node-role.kubernetes.io/control-plane and node-role.kubernetes.io/etcd. Since the etcd-role is not a kubernetes standard, manifests/charts containing tolerations to allow execution on the control-plane, for example kubevirt, still fail to run on rke2/k3s clusters due to the etcd taint.

I'd like to suggest to only set the etcd-taint on nodes not having the control-plane role at the same time. That way dedicated etcd clusters will be left alone even if a deployment has the toleration for control-plane nodes. Combined nodes with etcd and control-plane on the same host would then be able to get workloads designated to the control-plane.

// cc: @iholder101 from the kubevirt project

[github-actions[bot]]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.

[max06]

This is not solved.

And no reaction after 2 months in a project like this is a shame...

[github-actions[bot]]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.