Event Endpoint Management continues to be enhanced

Event Endpoint Management continues to be available and enhanced as part of IBM's integration platforms.

End of Marketing announcement for IBM Event Automation

Event Streams and Event Processing are deprecated and no enhancements will be provided. Support and security fixes will be provided in line with published support lifecycle policies. Future event-driven solutions that make use of Apache Kafka and Apache Flink will be delivered by IBM Confluent.

For more information, see the support lifecycle transition and software ordering completion announcement.

Attention: This version of Event Streams has reached End of Support. For more information about supported versions, see the support matrix.

Admin API pod does not start when using OpenShift 4.6

Symptoms

The Admin API pod fails to start when creating an Event Streams instance on OpenShift Container Platform version 4.6, reporting a mount failure for volume kube-root-ca.

Causes

The Event Streams Admin API pod uses the OpenShift Container Platform ingress to query metrics data from Prometheus. The UI can then display the metrics in the monitoring and topics pages.

The REST client issuing the query requires access to the ingress CA certificate. The certificate exists in a ConfigMap called kube-root-ca.crt. This ConfigMap is injected into all namespaces on OpenShift Container Platform version 4.7 and later, but does not exist on version 4.6 and earlier.

Resolving the problem

In the namespace where you are installing the Event Streams instance, create a ConfigMap called kube-root-ca.crt and add the CA certificate to the ConfigMap. You can do this by copying the contents of the default-ingress-cert ConfigMap from the openshift-config-managed namespace as follows:

oc get cm default-ingress-cert --namespace=openshift-config-managed -o yaml | sed 's/name: default-ingress-cert/name: kube-root-ca.crt/' | sed 's/namespace: openshift-config-managed/namespace: <target-namespace>/' | oc create -f -