-
Story
-
Resolution: Done
-
Major
-
7.5.0.CR1
-
None
User Story:
As a System Administrator
I would like to be able to configure the DNS Service to use different protocols and ports etc
so that I can have more than 1 AMQ 7 Clusters within the same Openshift namespace
More Info:
As there is no technical reason why it shouldn't be possible to have two separate AMQ clusters in the same namespace, the DNS ping service should not be hardcoded to "ping" , but instead be parameterized in the templates
Also, the ping service name should be prefixed by ${APPLICATION_NAME}- in the templates, so that it is possible to instantiate the template more than once for separate clusters in the single namespace.
- is cloned by
-
CLOUD-2662 [AMQ7] don't hardcode openshift.DNS_PING service name
- Closed
- is related to
-
ENTMQBR-2778 Secret credential name not dynamic preventing multiple deployments per project namespace
- Closed
-
ENTMQBR-2875 Static headless and ping service names prevent more than one custom resource instance per namespace
- Closed
-
ENTMQBR-1857 Document 7.5 Operator: Document don't hardcode openshift.DNS_PING service name
- Closed
- relates to
-
ENTMQBR-2980 Ensure name and label generation works for the multi-statefulset case
- Closed
-
JGRP-2363 DNS Ping cannot lookup SRV record for service port
- Closed
-
ENTMQBR-4029 Different exceptions related to DNS SRV raised at the startup of the broker
- Closed
-
ENTMQBR-3400 Doc: [OCP] Ensure name and label generation works for the multi-statefulset case
- Closed