[idea] helm-operator event/hook system

[SimonBaeumer]

Feature Request

Describe the problem you need a feature to resolve.

To maintain a helm-chart and an operator in parallel we would like to re-use as much as possible from our helm-chart.
Given that helm is limited in it's feature set the helm-operator can only support Level II operators.
I started trying to re-invent the wheel to render the k8s objects based on our helm-chart and do everything the helm-operator does only to interact under specific circumstances differently, i.e. creating backups or recovering from an error.

Describe the solution you'd like.

I am looking for a way to create a Go controller which uses the helm-operator but gives me the ability to customize at specific lifecycle events.
A basic idea would be to create an event-system or callback functions which are executed at specific events like installation, reconciliation or deletion. This would give me the chance to look at the current state and decide how to proceed before helm applies any changes.

Further it would allow us to created CRDs which are independent from our values.yaml and overall more flexibility.

I am curios what you are thinking about this approach.

Thanks in advance!

Best regards,
Simon

[SimonBaeumer]

The issue #670 about supporting hybrid operators could be related to this idea.

[estroz]

Great request! In fact, a redesign of the helm-operator's API is in flight that adds hook registration amongst other things.

[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

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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.