helmify VS autobucket-operator

Exactly this. No need to wrap your app that only you consume and deploy as a helm chart. If you want to benefit from Helms application management features like rollbacks, you can use helm-x or helmify

[1] https://github.com/edgelesssys/constellation/tree/main/operators/constellation-node-operator [2] https://github.com/edgelesssys/constellation/blob/main/bootstrapper/internal/kubernetes/kubernetes.go#L350 [3] https://olm.operatorframework.io/docs/ [4] https://github.com/arttor/helmify [5] https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-tcp-reset

For this demo I have created a Kubernetes cluster (v1.18.6), a GCP project, and a GCP service account (detailed GCP instructions here). Then we’ll install our resources and controller manager:

The operator provides a special deployment annotation “ab.leclouddev.com/on-delete-policy” which can be set to “destroy” or “ignore”. If it is set to “destroy” as in our example above, the operator will delete the Cloud Storage bucket when the Bucket CR is deleted, and also when the Deployment is deleted since a Deployment deletion triggers a Bucket CR deletion (use carefully as you might lose data). This is done through Kubernetes Finalizers, which I highly encourage you to read on, and you can check the full code here.