Add top-level notificationsBus configuration#694
Add top-level notificationsBus configuration#694arxcruz merged 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
lmiccini
commented
Feb 7, 2026
- Add notificationsBus.cluster to all telemetry-enabled deployments
- Use rabbitmq-notifications for va/hci and dt/uni05epsilon (dedicated cluster)
- Use rabbitmq for all other deployments (default cluster)
- Add notificationsBus.cluster: rabbitmq to all other service-values files as placeholder to enable kustomize component to work universally
- Create lib/control-plane/messaging-bus kustomize component to inject notificationsBus from service-values ConfigMap into spec.notificationsBus
- Remove deprecated nova.notificationsBus replacements from kustomization files (replaced by top-level spec.notificationsBus)
- Update va/hci and dt/uni05epsilon to use new notificationsBus.cluster format instead of deprecated notificationsBusInstance
4896475 to
50459b1
Compare
|
please explain the template repurposing, in ci-framework-jobs downstream there is a lots of configurations relying on paths with |
This commit introduces a new messaging bus configuration structure while replacing deprecated field names with their modern equivalents. Changes: - Add notificationsBus.cluster to all service-values files - Use rabbitmq-notifications for va/hci and dt/uni05epsilon (dedicated cluster) - Use rabbitmq for all other deployments (default cluster) - Replace cellMessageBusInstance with messagingBus.cluster in nova cells - Replace notificationsBusInstance with top-level notificationsBus.cluster - Create lib/control-plane/messaging-bus kustomize component to inject notificationsBus from service-values ConfigMap into spec.notificationsBus - Update va/hci and dt/uni05epsilon kustomization files to use new messaging-bus component instead of manual notificationsBusInstance replacement - Update documentation (README files) to reflect new messagingBus structure Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: arxcruz, lmiccini 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 |
|
/cherry-pick 18.0-fr5 |
|
@karelyatin: new pull request created: #703 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |