-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⚠️ Remove support for API/conductor split #487
Conversation
Signed-off-by: Dmitry Tantsur <[email protected]>
Signed-off-by: Dmitry Tantsur <[email protected]>
Signed-off-by: Dmitry Tantsur <[email protected]>
Signed-off-by: Dmitry Tantsur <[email protected]>
/test-centos-integration-main |
/test-centos-integration-main |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elfosardo The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
…orter-414 OCPBUGS-32364: [4.14] remove unused prometheus-exporter
Running API and conductor separately mostly makes sense in the context of large OpenStack clouds. We used to use it before the all-in-one executable appeared, but now it's untested and potentially broken.
While here, enforce authentication for JSON RPC and clean up related options.