RKE2 and Nginx Ingress Controller

Hello!
I have an RKE2 cluster that consists of 3 masters and 3 workers. Installed according to the documentation. I empirically found that the Nginx Ingress Controller is available only on Master 1. Can I make it available on other masters?

└─# kubectl get nodes
NAME          STATUS   ROLES         AGE   VERSION
cuba-kub-01   Ready    etcd,master   45d   v1.18.10+rke2r1
cuba-kub-02   Ready    etcd,master   44d   v1.18.10+rke2r1
cuba-kub-03   Ready    etcd,master   44d   v1.18.10+rke2r1
cuba-kub-04   Ready    node          44d   v1.18.10+rke2r1
cuba-kub-05   Ready    node          44d   v1.18.10+rke2r1
cuba-kub-06   Ready    node          44d   v1.18.10+rke2r1

Hi,

just playing around with rke2 too (nice new toy, looks promising). This is an old topic but maybe someone needs a solution for this too. If I got it right, the way to do it is to write a HelmChartConfig into the manifest directory.
I suppose it will only work if at least three master nodes are in the cluster. Until then, the replica set
remains in pending state.

(See answer from brandond here: HelmChartConfig modifications not taking effect · Issue #663 · rancher/rke2 · GitHub)

sudo tee /var/lib/rancher/rke2/server/manifests/rke2-ingress-nginx-config.yaml >> /dev/null << EOF
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
  name: rke2-ingress-nginx
  namespace: kube-system
spec:
  valuesContent: |-
    controller:
      nodeSelector:
        node-role.kubernetes.io/master: "true"
      replicaCount: 3
EOF

Or in a running cluster just to scale the deployment: Deployments | Kubernetes

Kind regards,
Michael