Stop Event Streams instance

I believe it would be beneficial for many customers, certainly mine, to be able to stop their Event Streams instances for many reasons:

1. The customer may require to stop their Event Streams instances so that they can undergo maintenance (at OpenShift cluster level, external storage cluster level, etc)
2. The customer may require to stop their Event Streams instances so that they can execute a backup.
3. The customer may require to stop their Event Streams instances so that they can power off IaaS instances they may have on the cloud.
4. Others

I believe the operator framework came in to take on these kind of administration tasks, easing the use of containerized technologies over traditional deployments. As a result and as a client, I would expect the IBM Event Streams operator to help me with as many administrative tasks as possible and, of course, on a declarative manner. Hence, I would expect the IBM Event Streams operator to be able to stop an Event Streams instance under its control for me to carry out any of the tasks listed above. I would expect to be able to tell the IBM Event Streams operator to stop an instance pretty much in the same way I do with a Kafka Connect or a Mirror Maker instance. That is, setting a property on their YAML spec.
 

A customer should not need to understand the complexities of properly stop a kafka instance on a controlled manner. The operator framework came in to hide such complexities and that is what I, as a customer, would expect from the enterprise ready verision of IBM Event Streams.