You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hcloud CCM can be deployed either as DaemonSet or as Deployment. --leader-elect=false must only be used in a deployment with 1 replica. In a DaemonSet or Deployment with more than 1 replica --leader-elect=false must not be used.
What happened?
I just noticed that the start parameters to hcloud-cloud-controller-manager in external-hcloud-cloud-controller-manager-ds-with-networks.yml.j2 and external-hcloud-cloud-controller-manager-ds.yml.j2 differs from the parameters used in the original project.
Hcloud CCM can be deployed either as DaemonSet or as Deployment.
--leader-elect=false
must only be used in a deployment with 1 replica. In a DaemonSet or Deployment with more than 1 replica--leader-elect=false
must not be used.Also the use of newly introduced parameters
--route-reconciliation-period=30s
and--webhook-secure-port=0
should be considered. See comment in https://github.com/hetznercloud/hcloud-cloud-controller-manager/blob/main/chart/values.yamlWhat did you expect to happen?
Correct parameters should be used
How can we reproduce it (as minimally and precisely as possible)?
n/a
OS
n/a
Version of Ansible
n/a
Version of Python
n/a
Version of Kubespray (commit)
2.27.0
Network plugin used
calico
Full inventory with variables
n/a
Command used to invoke ansible
n/a
Output of ansible run
n/a
Anything else we need to know
No response
The text was updated successfully, but these errors were encountered: