Skip to content

Kraan does not recognize healthCheckExprs on HelmRelease kind #470

Description

@kishoregv

Is your feature request related to a problem? Please describe.
Kraan fails to parse and validate healthCheckExprs fields on HelmRelease objects. When a HelmRelease specifies CEL-based custom health check expressions, kraan does not recognize the
field because the fluxcd/helm-controller/api dependency is pinned at v1.1.0, which predates the introduction of healthCheckExprs in the HelmRelease spec.

Expected Behavior:

Kraan should correctly parse HelmRelease objects that include spec.healthCheckExprs and properly evaluate layer health status based on these CEL expressions.

Root Cause:

The github.com/fluxcd/helm-controller/api Go module at v1.1.0 does not include the healthCheckExprs field in its HelmRelease type definition. This field was introduced in
helm-controller v1.5.0 as part of the Helm v4 upgrade.

Describe the solution you'd like

Bump the following dependencies:

  • github.com/fluxcd/helm-controller/api v1.1.0 → v1.5.4
  • github.com/fluxcd/source-controller/api v1.4.1 → v1.8.3
  • github.com/fluxcd/pkg/apis/meta v1.25.1 → v1.26.0
  • Chart image tags: helm-controller v1.5.3 → v1.5.4, source-controller v1.8.1 → v1.8.3

Bugs Fixed by helm-controller v1.5.3 → v1.5.4

v1.5.4

  • Fix post-renderer conflict of overlapping hooks and templates (#1461) — resolves issues where charts with both hooks and templates sharing resource names would conflict during
    post-rendering
  • Ignore force-replace when server-side apply is enabled (#1456) — prevents invalid force-replace operations under SSA
  • Preserve line endings in SplitManifests — fixes downstream YAML parser issues

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions