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.

Stopping and starting Event Streams

You can stop your Event Streams cluster if required, for example, in preparation for maintenance.

Use the following instructions to gracefully shut down your Event Streams cluster. You can then start the cluster up again when it is ready.

Stopping

To shut down your cluster gracefully, scale all deployments and stateful sets to 0 replicas as follows.

  1. Log in to your cluster as an administrator by using the IBM Cloud Private CLI:
    cloudctl login -a https://<cluster-address>:<cluster-router-https-port>

  2. Retrieve all deployments and stateful sets in your Event Streams namespace associated with the release, and scale them down to 0 replicas:

     kubectl get deployments -n <namespace> -l release=<release-name> -o custom-columns=NAME:.metadata.name,REPLICAS:.spec.replicas --no-headers > <deploy-replicas-filename> && while read -ra deploy; do kubectl -n <namespace> scale --replicas=0 deployment/${deploy}; done < <deploy-replicas-filename>
     kubectl get sts -n <namespace> -l release=<release-name> -o custom-columns=NAME:.metadata.name,REPLICAS:.spec.replicas --no-headers > <sts-replicas-filename> && while read -ra sts; do kubectl -n <namespace> scale --replicas=0 sts/${sts}; done < <sts-replicas-filename>
    

Where:

  • <namespace> is the location of your installation.
  • <release-name> is the name that identifies your Event Streams installation.
  • <deploy-replicas-filename> is the file where deployment - replica pairs are to be saved (provide a name, for example, deploy-replicas.yaml).
  • <sts-replicas-filename> is the file where stateful set - replica pairs are to be saved (provide a name, for example, sts-replicas.yaml).

Starting up

To start up your cluster and scale it back up to its previous state, run the following commands.

  1. Log in to your cluster as an administrator by using the IBM Cloud Private CLI:
    cloudctl login -a https://<cluster-address>:<cluster-router-https-port>

  2. Retrieve and apply the previous configuration for your Event Streams instance:

     while IFS= read -ra deploy; do d=$(echo $deploy | cut -f1 -d" "); rep=$(echo $deploy | cut -f2 -d" "); kubectl -n <namespace> scale --replicas=$rep deployment/${d}; done < <deploy-replicas-filename>
     while IFS= read -ra sts; do s=$(echo $sts | cut -f1 -d" "); rep=$(echo $sts | cut -f2 -d" "); kubectl -n <namespace> scale --replicas=$rep sts/${s}; done < <sts-replicas-filename>
    

Where:

  • <namespace> is the location of your installation.
  • <deploy-replicas-filename> is the file where you saved deployment - replica pairs (for example, deploy-replicas.yaml).
  • <sts-replicas-filename> is the file where you saved stateful set - replica pairs (for example, sts-replicas.yaml).