Description of problem (please be detailed as possible and provide log snippets): - The Noobaa-endpoint pod should be configurable as HA. - We have HPA configured for noobaa-endpoint deployment but the parameters can't be configured. - The MINPODS and MAXPODS values are set to 1 and 2. If we try to change these values it gets reconciled. - The requirement is the ability to configure the noobaa-endpoint pod in high availability. - The MINPODS and MAXPODS can be configured accordingly so that during any activity on the cluster the noobaa services won't be impacted. - We can additionally add the pod-affinity on it so that no two endpoint pods are running on one node. - In this way we can maintain the HA for noobaa-endpoint. Version of all relevant components (if applicable): v4.10 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? - During upgrades the pods get restarted, if noobaa-endpoint is configured in HA the services won't be impacted during the pod restarts. Is there any workaround available to the best of your knowledge? N/A Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 3 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: No Steps to Reproduce: 1. Edit the HPA with the required values. 2. Verify the changes in HPA. 3. The values of HPA get reconciled. Actual results: - The parameters of HPA get reconciled. Expected results: - The parameter of HPA should be configurable. Additional info: - In the next comments.
With the current implementation of ODF 4.14 (build 4.14.0-126), the MINPODS and MAXPODS values are set to 1 and 2 as default. They get reconciled if the values are changed. These values got pushed from ocs-operator. Nimrob, please advise what should we do with this issue.
The min and max are already supported to be changed and not reconciled on previous versions. So this BZ is essentially on the topology constraint. If there was a regression in the ocs op and now its reconciling to 1-2 then we should open a new BZ on the ocs-op for this regression.
Closing this issue with the current implementation of Noobaa-endpoint in ODF 4.14.