[ws-manager-mk2] Configure leader election

[WVerlaek]

Description

Configure leader election on the ws-manager-mk2 controller manager. Requires additional role policy rules to manage leases, these rules are taken from the generated leader_election_role.yaml by kubebuilder

Related Issue(s)

Relates to #11416

How to test

Open preview env, check logs of ws-manager-mk2 to confirm a leader-election lease has been successfully acquired

Release Notes

NONE

Documentation

Build Options:

• /werft with-github-actions
  Experimental feature to run the build with GitHub Actions (and not in Werft).
• leeway-no-cache
  leeway-target=components:all-ci
• /werft no-test
  Run Leeway with --dont-test

Preview Environment Options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft with-wsman-mk2
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[Furisto]

/werft run with-preview

👍 started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.1
(with .werft/ from main)

[Furisto]

/werft run with-preview -with-wsman-mk2

👍 started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.2
(with .werft/ from main)

[WVerlaek]

/werft run with-preview with-wsman-mk2 with-large-vm

👍 started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.3
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.4 because the annotations in the pull request description changed
(with .werft/ from main)

[WVerlaek]

/werft run

👍 started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.6
(with .werft/ from main)

[WVerlaek]

/werft run

👍 started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.7
(with .werft/ from main)

[WVerlaek]

/werft run recreate-vm

👍 started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.9
(with .werft/ from main)

[kylos101]

/werft run with-integration-tests=workspace with-large-vm=true

👍 started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.10
(with .werft/ from main)

[kylos101]

Ran following tests:

1. Confirmed leader election starts and can finish
2. Deleted single pod, election happens again flawlessly, sometimes the new pod is the leader
3. Scaled up a second pod, the election starts, and never finishes, because there's a current leader
4. Scaled up a second pod, cordoned the node, deleted the current leader, and leadership transitioned to the second pod, the third pod was pending because of cordoning

Nice! Works as designed!

[kylos101]

✔️

[WVerlaek]

/werft run

👍 started the job as gitpod-build-wv-ws-manager-mk2-leader-elect.11
(with .werft/ from main)