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 resources are unexpectedly missing from the cluster

Symptoms

Flink resources such as Service, Deployment, ReplicaSet, Pod, and ConfigMap are not found in the cluster, and the following status is displayed in the FlinkDeployment custom resource:

status:
  jobManagerDeploymentStatus: MISSING

Causes

This error might occur because the Flink Kubernetes Operator is configured to clean up Flink resources one day after a job reaches its terminal state. This behavior is controlled by the kubernetes.operator.jm-deployment.shutdown-ttl configuration.

Resolving the problem

To resolve the problem, ensure you follow the steps provided in the recover Flink deployment troubleshooting. Additionally, complete any one of the following steps to help prevent this issue in the future:

  • To apply to all the FlinkDeployment custom resources managed by the operator, edit the Flink Kubernetes Operator ConfigMap flink-operator-config, and add the following key to the flink-conf.yaml section:

    data:
  flink-conf.yaml: |
      kubernetes.operator.jm-deployment.shutdown-ttl: 7 d

    To edit a ConfigMap by using the CLI, run the following command:

     kubectl edit configmap `flink-operator-config` -n <target-namespace>

    The ConfigMap flink-operator-config is available by default in the namespace where IBM Operator for Apache Flink is installed.

  • To set the configuration in a specific FlinkDeployment custom resource, add the following key to the spec.flinkConfiguration section:

    spec:
  flinkConfiguration:
      kubernetes.operator.jm-deployment.shutdown-ttl: 7 d