You can stop or shut down your Event Streams instance if required. You might want to do this in cases of hardware maintenance or during scheduled power outages.
Use the following instructions to gracefully shut down your Event Streams instance. The instance can be started again following the starting up Event Streams instructions.
Stopping Event Streams
To shut down your cluster gracefully, uninstall the operator to ensure your Event Streams instance is no longer managed and scale all components to 0 replicas as follows:
Stop the operator
- Log in to the OpenShift Container Platform web console using your login credentials.
- Expand the Operators dropdown and select Installed Operators to open the Installed Operators page.
- Expand the Project dropdown and select the project the instance is installed in. Click the operator called IBM Event Streams managing the project.
- Select the Actions dropdown and click Uninstall Operator.
Scale down components
After the operator has uninstalled, you can safely scale down all components to 0 replicas, ensuring no pods are running.
To do this for all components of type Deployment, run:
kubectl get deployments -n <namespace> -l app.kubernetes.io/instance=<instance-name> -o custom-columns=NAME:.metadata.name,REPLICAS:.spec.replicas --no-headers > deployment.txt && while read -ra deploy; do kubectl -n <namespace> scale --replicas=0 deployment/${deploy}; done < deployment.txt
Where <namespace> is the namespace your Event Streams instance is installed in and <instance-name> is the name of your Event Streams instance.
Note: This saves the state of your deployments to a file called deployment.txt in the current working directory.
To do this for all components of type StatefulSet, run:
kubectl get sts -n <namespace> -l app.kubernetes.io/instance=<instance-name> -o custom-columns=NAME:.metadata.name,REPLICAS:.spec.replicas --no-headers > sts.txt && while read -ra sts; do kubectl -n <namespace> scale --replicas=0 sts/${sts}; done < sts.txt
Where <namespace> is the namespace your Event Streams instance is installed in and <instance-name> is the name of your Event Streams instance.
Note: This saves the state of your stateful sets to a file called sts.txt in the current working directory.
Starting up Event Streams
To scale the Event Streams instance back up to the original state, install the Event Streams operator again following the steps in the installing section.
- Install the operator, ensuring it is configured with the same installation mode as used for the previous installation.
- Wait for the operator to scale all resources back up to their original state. You can watch the progress by running:
oc get pods --watch