Long release name causes 503 errors

[gmcrobert]

Issue Description

When a helm chart is installed with a release name that is longer than 15 characters, the system starts up normally but any Kafka operations in the user interface or command line interface, e.g. topic create, will result in a 503 error notification being displayed.

The longer release name causes the system to truncate the pod names which introduces an issue where the non-truncated version of the name is used in accessing the Kafka brokers.

Issue resolution

The code is changed to correctly use the truncated names throughout so the lookup no longer fails

Workaround

Re-install the helm chart with a release name that is shorter than 15 characters

Fix details

IBM internal issue number - 3705
Fix target - 2019.4.1