Skip to content

audit every operator-backed application for a missing dependsOn edge #3850

Description

@myasnikovdaniil

Two operator-backed applications shipped without a dependsOn edge to the operator that serves their CRD: etcd, fixed in #3817, and mongodb, fixed in #3845. Both were found by accident while working on something else, not by looking.

The failure is quiet in both directions. At install a tenant can create the application before the CRD exists, and its HelmRelease fails with no matches for kind .... In CI the operator's own package reaches no runnable suite, so every change to it escalates to the full 21-suite run.

Worth walking every *-application source in packages/core/platform/sources/ against the apiVersion its chart actually renders and confirming the edge, rather than waiting for the third one to turn up.

Activity

  1. added
    kind/cleanupCategorizes issue or PR as related to cleanup of code, process, or technical debt
    triage/needs-triageIndicates an issue needs triage by a maintainer
    area/ciIssues or PRs related to CI workflows, GitHub Actions, automation
    on Aug 16, 2026
  2. added
    area/platformIssues or PRs related to platform infrastructure (bundle, flux, talos, installer)
    triage/acceptedIndicates an issue is ready to be actively worked on
    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release
    and removed
    triage/needs-triageIndicates an issue needs triage by a maintainer
    on Sep 23, 2026
  3. added a commit that references this issue on Sep 30, 2026
    b86fd7a
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

    area/ciIssues or PRs related to CI workflows, GitHub Actions, automationarea/platformIssues or PRs related to platform infrastructure (bundle, flux, talos, installer)kind/cleanupCategorizes issue or PR as related to cleanup of code, process, or technical debtpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next releasetriage/acceptedIndicates an issue is ready to be actively worked on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions