Unable to connect clients to bootstrap url when on OpenShift

[nictownsend]

Issue Description

When deploying an instance of Event Streams 2019.4.2 on OpenShift, clients connecting via the external bootstrap URL presented in the UI may encounter connection issues where Kafka is not contactable.

This can occur when OpenShift generates truncated routes for Kafka listeners, but the Kafka listeners are not updated with the truncated values.

Diagnosis

To diagnose, run the following commands:

• oc get routes
• oc describe cm <release>-ibm-es-proxy-cm

Compare the values for HOST/PORT of the following routes against the externalListeners section of the config map:

• <release>-ibm-es-proxy-route-broker-<0..n>
• <release>-ibm-es-proxy-route-bootstrap

If any of the routes do not match the listeners, the config map will need to be updated

Resolution

1. If the bootstrap listener does not match the bootstrap route:

   • The route will take the following form: <prefix>-<namespace>.<domain>:443 eg es-1-ibm-es-proxy-route-bootstrap-mynamespace.domain.somewhere:port
   • set the bootstrapRoutePrefix in the config map to es-1-ibm-es-proxy-route-bootstrap (do not save changes yet)

2. If the broker listeners do not match the broker route:

   • The route will take the following form: <prefix>-<broker-id>-<namespace>.<domain>:443 eg es-1-ibm-es-proxy-route-broker-1-mynamespace.domain.somewhere:port
   • set the brokerRoutePrefix in the config map to es-1-ibm-es-proxy-route-broker- (do not save changes yet)

3. Change the revision value in the config map to 1 greater than the current value. You can now save the config map changes.

Environment

• IBM Event Streams Version: 2019.4.2 deployed on Openshift

Internal issue: 5957
Fixed in: 10.0