Flaky test case Operator HA Upgrades when locality based exclusions are used and the resources are limited in a satellite namespace

[johscheuer]

What happened?

When the global mode is used the test case Operator HA Upgrades when locality based exclusions are used and the resources are limited in a satellite namespace is flaky. We should investigate those test failures and make changes either to the test case or the operator to ensure the test passes and validates the expected upgrade path.

What did you expect to happen?

Test should pass consistently .

How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?

No response

FDB Kubernetes operator

$ kubectl fdb version
# paste output here

Kubernetes version

$ kubectl version
# paste output here

Cloud provider