[deckhouse-controller] ha

[miklezzzz]

Description

Provides HA mode based on leases and leader election for deckhouse deployment.
Relates to flant/addon-operator#454

Why do we need it, and what problem does it solve?

It allows to have multiple deckhouse pods, running simultaneously, with a dedicated leader, holding the lease and doing the operator's job. In case of the leader not capable of renewing the lease in a certain amount of time, a new leader is elected among other pods and the new elected leader is promoted to do all the operations.
Closes #4163

What is the expected result?

The expected result is that it's possible to set deckhouse module to run in highavailability mode via its module settings.

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: deckhouse-controller
type: feature
summary: Provides Deckhouse HA mode.
impact_level: default

[deckhouse-BOaTswain]

🟢 e2e: Yandex.Cloud for deckhouse:deckhouse-controller-ha succeeded in 41m24s.

Workflow details

Yandex.Cloud-WithoutNAT-Containerd-1.25 - Connection string: ssh [email protected]

🟢 e2e: Yandex.Cloud, Containerd, Kubernetes 1.25 succeeded in 40m44s.

[miklezzzz]

[miklezzzz]

standby pod's logs

[miklezzzz]

lease and endpoints