[#105] Drainer pod uses un-resolvable hostname for it's cluster connection

[gaohoward]

Thanks for submitting your Pull Request!

Please make sure your PR meets the following requirements:

• Pull Request title is properly formatted: [CLOUD-XYA] Subject
• Pull Request contains link to the JIRA issue
• Pull Request contains description of the issue
• Pull Request does not include fixes for issues other than the main ticket
• Attached commits represent units of work and are properly formatted
• You have read and agreed to the Developer Certificate of Origin (DCO) (see CONTRIBUTING.md)
• Every commit contains Signed-off-by: Your Name <yourname@example.com> - use git commit -s

[brusdev]

An alternative solution to the IP address is to pass the full hostname as the Operator does for jolokia client, see https://github.com/artemiscloud/activemq-artemis-operator/blob/main/pkg/utils/jolokia_client/jolokia_client.go#L75

[gaohoward]

An alternative solution to the IP address is to pass the full hostname as the Operator does for jolokia client, see https://github.com/artemiscloud/activemq-artemis-operator/blob/main/pkg/utils/jolokia_client/jolokia_client.go#L75

That may not work. The problem is that the drainer pod is a standalone pod and the DNS record for the pod may not be even generated (because it is not part of the headless service any more). To get a valid resolvable record some more configurations need to be added for this pod. So I think the IP address solution is the simple one to go.