Pause and Resume watch/reconcile of custom resource by helm-operator

[sukhil-suresh]

Feature Request

Describe the problem you need a feature to resolve.

For a particular scenario, we temporarily scale down a deployment (which is part of our product) by updating the replica value to zero in the spec. However, it seems the helm-operator-controller interferes with this and scales it back up to the replica count set for the operand install.

Describe the solution you'd like.

It would be very helpful if the helm controller could temporarily pause reconciliation for a resource and then resume later. Maybe this could be triggered by a paused annotation on the resource?

The operator-lib project has support for such a feature - operator-framework/operator-lib#60

If such a feature already exists for the helm-operator, kindly guide us with the related resource.

/language helm

[varshaprasad96]

@sukhil-suresh Unfortunately, we don't have this feature in Helm operators. The available set of annotations for Helm operators are here: https://sdk.operatorframework.io/docs/building-operators/helm/reference/advanced_features/annotations/.

[sukhil-suresh]

@varshaprasad96 Thanks for sharing the annotations supported by the Helm operator.

We have an (untested) workaround for the problem we faced, which involves updating the operand spec to have support for the deployment replica. The assumption is that the helm operator will respect the operand spec value change.

Feel free to close the issue, if needed. I still believe there is value in an annotation that allows pause/resume of the helm-based operator reconciliation.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[sukhil-suresh]

/close

[openshift-ci]

@sukhil-suresh: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.