If the cluster is not available we shouldn't perform automatic replacements as the operator is not able to make any good decision. The operator will not replace more than MaxConcurrentReplacements in the worst case, but I still think it's better to skip this feature at all if the cluster is unavailable.
Type of change
Please select one of the options below.
Bug fix (non-breaking change which fixes an issue)
Description
If the cluster is not available we shouldn't perform automatic replacements as the operator is not able to make any good decision. The operator will not replace more than
MaxConcurrentReplacements
in the worst case, but I still think it's better to skip this feature at all if the cluster is unavailable.Type of change
Please select one of the options below.
Discussion
-
Testing
CI will run e2e tests.
Documentation
-
Follow-up
-