Use OpenStack CR operatorOverrides to scale down placement operator#411
Use OpenStack CR operatorOverrides to scale down placement operator#411karelyatin wants to merge 1 commit into
Conversation
Switch from CSV-based scaling to using OpenStack CR operatorOverrides feature for scaling down the placement operator. This avoids the need to disable the openstack init operator and provides better integration with the OpenStack operator management system. Signed-off-by: Yatin Karel <ykarel@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: karelyatin The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/lgtm |
|
oh i do not have an env to test this myself currently but this makes sense it would have nice to call that out a little more explcity in the PR body im not going to appove this mearly be cause we do not have ci testign fo this as far as im aware and i have not verified it works locally but i have no objection to this change. |
Switch from CSV-based scaling to using OpenStack CR operatorOverrides
feature for scaling down the placement operator. This avoids the need
to disable the openstack init operator and provides better integration
with the OpenStack operator management system.