Missing "cluster-init" option in config.yaml in the only control plane node. about terraform-hcloud-kube-hetzner HOT 4 OPEN

Hey,

I was referring to "Backup and restore a cluster" guide in https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner?tab=readme-ov-file#examples.

The postinstall_exec script there contains:

 export CLUSTERINIT=$(cat /etc/rancher/k3s/config.yaml | grep -i '"cluster-init": true')
      if [ -n "$CLUSTERINIT" ]; then
        echo indeed this is the first control plane node > /tmp/restorenotes

which kind of assumes the first control plane node is special.

from terraform-hcloud-kube-hetzner.

I think the initial config created with null_resources.first_control_plane is overridden by null_resource.control_plane_config. Is this intended? Perhaps in locals.k3s-config we should add something like cluster-init: k == 0?

from terraform-hcloud-kube-hetzner.

@mateuszlewko Yes, indeed we override it as to not make the first control-plane special. Could you please explain your proposed solution for the restore flow, not sure I follow.

from terraform-hcloud-kube-hetzner.

@mateuszlewko Ah yes, so that needs to change, PR welcome to correct this example, please.

from terraform-hcloud-kube-hetzner.