Removing resources

Removing the Flink Operator and its resources before intalling a newer version of the Cloudera Streaming Analytics - Kubernetes Operator.

Before installing a newer version of the Cloudera Streaming Analytics - Kubernetes Operator, you need to ensure that the Flink Operator and its resources are deleted from your namespace(s). Simply uninstalling the Cloudera Streaming Analytics - Kubernetes Operator does not mean that all of the resources are removed from the cluster.

Remove the Flink Operator using the following command:
```
helm uninstall flink-operator -n flink
```
When deleting the Flink Operator, the following message indicates which resources remain in the namespace:
```
These resources were kept due to the resource policy:
[RoleBinding] flink-role-binding
[Role] flink
[ServiceAccount] flink
[PersistentVolumeClaim] postgreSQL
```
In case the PostgreSQL (or other database) persistent volume claim is not removed, the SQL project and job related data is stored in the database.

Remove the remaining resources using kubectl:

kubectl delete rolebinding flink-role-binding -n flink
kubectl delete role flink -n flink
kubectl delete serviceaccount flink -n flink

Update the Cloudera Streaming Analytics CRDs using the following commands:

helm template oci://container.repository.cloudera.com/cloudera-helm/csa-operator/csa-operator --version 1.1.2-b17 --include-crds --output-dir .

kubectl replace -f csa-operator/charts/flink-kubernetes-operator/crds/flinkdeployments.flink.apache.org-v1.yml

kubectl replace -f csa-operator/charts/flink-kubernetes-operator/crds/flinksessionjobs.flink.apache.org-v1.yml