You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[epic] operator-controller rejects helm charts that use helm hooks #995
In order to reduce the scope of an initial implementation of helm support in operator-controller, should we proactively reject helm charts that ultimately include chart hooks in their manifests?
Supporting helm chart hooks generally means that we are using helm's libraries to manage the lifecycle of the objects, which has other implications (e.g. see #923).
It also means that there are additional complexities due to the stages introduced by chart hooks (e.g. it is generally not acceptable to block in a Reconcile implementation).
NOTE: This is not immediately important while we are only supporting registry+v1 bundles because operator-controller generates helm charts on-the-fly from registry+v1 bundle content, and it does not use chart hooks.
changed the title [-][epic] operator-controller reject helm charts that use helm hooks[/-][+][epic] operator-controller rejects helm charts that use helm hooks[/+]on Jul 1, 2024
Activity
[-][epic] operator-controller reject helm charts that use helm hooks[/-][+][epic] operator-controller rejects helm charts that use helm hooks[/+]LalatenduMohanty commentedon Oct 22, 2024
This epic is part of #962 but it is a significant piece which needs to represented separately.
github-actions commentedon Sep 6, 2025
Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.
github-actions commentedon Oct 6, 2025
This issue has been closed due to inactivity.