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.

Flink pods enter ImagePullBackOff state

Symptoms

When creating an instance of a FlinkDeployment in an offline Kubernetes environment, some pods might display an ImagePullBackOff error status after the instance is created.

Causes

The service account that is created to run the Flink instance does not reference the secret containing credentials to the private registry that is used to store the component images.

Resolving the problem

To resolve the error, add the ibm-entitlement-key to the service account:

apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    app.kubernetes.io/instance: ibm-eventautomation-flink
    app.kubernetes.io/managed-by: ibm-eventautomation-flink-operator
    app.kubernetes.io/name: ibm-eventautomation-flink
  name: flink
imagePullSecrets:
  - name: ibm-entitlement-key

Note: The secret ibm-entitlement-key is expected to be present in the namespace and is expected to contain credentials to the private registry that is being used to store the images.