User Request: Feature flag to disable deletion of Disruption

[nikos912000]

Is your feature request related to a problem? Please describe.
Our team is working on integrating the chaos controller with our CI/CD platform.

The setup we have is as follows:

• Kubefed acts as the control plane and propagates any changes to worker clusters.
• Worker clusters are the ones where workloads get deployed. These are the clusters where we run Disruptions.
• The Spinnaker pipeline deploys Disruptions to the worker clusters through Kubefed.

Right now the deletion of Disruptions is done by the controller. This is happening once the Disruption expires and after the GC period.
This is great, but with a control plane we tend to have kubefed handling the lifecycle of any resources deployed to worker clusters. Ideally the responsibility to delete Disruptions would be on Spinnaker and Kubefed.

Describe the solution you'd like
Introduce a toggle in the controller's ConfigMap which disables the deletion.

Describe alternatives you've considered
The other option for us is to set the GC to a very large value so Spinnaker/Kubefed are always the first ones to do the deletion.

Additional context
Let us know if you have any other ideas. If this can be solved in a different way happy to consider it!

[ptnapoleon]

Absolutely, happy to add this

[nikos912000]

Awesome, thank you.
Is it just checking this flag in here?
Happy to raise the PR.

[ptnapoleon]

Yes, more or less. I will have a PR for you to review today