Skip to content

[epic] operator-controller rejects helm charts that use helm hooks #995

Closed as not planned

Description

@joelanford

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.

Activity

  1. added
    v1.xIssues related to OLMv1 features that come after 1.0
    on Jul 1, 2024
  2. 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
  3. LalatenduMohanty commented on Oct 22, 2024

    @LalatenduMohanty
    Member

    This epic is part of #962 but it is a significant piece which needs to represented separately.

  4. github-actions commented on Sep 6, 2025

    @github-actions

    Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

  5. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 6, 2025
  6. github-actions commented on Oct 6, 2025

    @github-actions

    This issue has been closed due to inactivity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    epiclifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.v1.xIssues related to OLMv1 features that come after 1.0

    Type

    No type

    Projects

    • Status
      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions