[transporturl] support TLS, watch name rabbitmq cluster resource and EnvTests #153
Conversation
The rabbitmq transport url requested needs to be in the following format for tls: rabbit://<user>:<pwd>@<service>:5671/?ssl=1 * pass query `?ssl=1/0` depending of enabled disabled * When tls is enabled a different port is used by the cluster. The information is part of the rabbitmq secret. Lets get the port information always from the secret. Jira: OSPRH-1919
stuggi
requested review from
Deydra71 and
vakwetu
and removed request for
frenzyfriday
stuggi
force-pushed
the
transporturl_tls
branch
from
dcbf8a4 to
bca900b
Compare
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/da73b5ac692f415b993dfe765d4d7955 ❌ openstack-k8s-operators-content-provider FAILURE in 15m 00s |
|
/test infra-operator-build-deploy-kuttl |
2 similar comments
|
/test infra-operator-build-deploy-kuttl |
|
/test infra-operator-build-deploy-kuttl |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/a39d166bd74541aab59b1324ec291177 ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 02m 22s |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/39e6f57d798c4855b68e1447e868ba9c ✔️ openstack-k8s-operators-content-provider SUCCESS in 42m 03s |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/943d670579404d0fbd78dd8f8260c770 ❌ openstack-k8s-operators-content-provider FAILURE in 15m 09s |
|
recheck |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olliewalsh, stuggi 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 |
openshift-merge-bot
bot
merged commit 5eb2ad7
into
openstack-k8s-operators:main
support tls query
The rabbitmq transport url requested needs to be in the following format for tls:
rabbit://<user>:<pwd>@<service>:5671/?ssl=1?ssl=1/0depending of enabled disabledwatch for named rabbit cluster
When updates are performed to the rabbitmq cluster, like change from non tls to tls configuration the transporturl has to reconcile. This adds functionality to the transporturl controller to watch for the named rabbitmq cluster.
Add envtest for default and tls use case
Jira: OSPRH-1919