add var disable_hetzner_ccm

[pat-s]

This is needed to allow deploying HCCM standalone which is required when one wants to include robot servers, which is only possible when deploying HCCM using the helm chart due to some helm chart magic.

[mysticaltech]

thanks @pat-s

[mysticaltech]

Hey @pat-s, FYI, had to reverse this because it broke the deployment with the following error:

module.kube-hetzner.null_resource.kustomization (remote-exec): Connected!
module.kube-hetzner.null_resource.kustomization: Still creating... [20s elapsed]
module.kube-hetzner.null_resource.kustomization (remote-exec): + sed -i 's/^- |[0-9]\+$/- |/g' /var/post_install/kustomization.yaml
module.kube-hetzner.null_resource.kustomization (remote-exec): + timeout 360 bash
module.kube-hetzner.null_resource.kustomization (remote-exec): + kubectl apply -k /var/post_install
module.kube-hetzner.null_resource.kustomization (remote-exec): error: accumulating resources: accumulation err='merging resources from 'https://github.com/hetznercloud/hcloud-cloud-controller-manager/releases/download/v1.21.0/ccm-networks.yaml': may not add resource with an already registered id: Deployment.v1.apps/hcloud-cloud-controller-manager.kube-system': evalsymlink failure on '/tmp/kustomize-3994297745/releases/download/v1.21.0/ccm-networks.yaml' : lstat /tmp/kustomize-3994297745/releases: no such file or directory
module.kube-hetzner.null_resource.agents["0-0-agent-small"]: Still creating... [1m0s elapsed]

If you want to resubmit, please test it well and please explain better how it works.

[pat-s]

Strange. I am using it since some time in my fork in exactly this variant without issues.

[pat-s]

@mysticaltech I just tried again and was unable to reproduce the failure. I'll open another PR and maybe others can give it a try, too. Or maybe you could add how you tested it?