[RFC-XXXX] Advanced Dependency Management - #5988
Open
vecil wants to merge 1 commit into
Open
Conversation
vecil
force-pushed
the
docs/propose-rfc-0014-advanced-dependency-management
branch
2 times, most recently
from
July 14, 2026 15:11
461f536 to
6e55730
Compare
vecil
changed the title
Signed-off-by: vecil <vincent.dely@ik.me> Assisted-by: claude-code/claude-fable-5
vecil
force-pushed
the
docs/propose-rfc-0014-advanced-dependency-management
branch
from
July 14, 2026 15:16
6e55730 to
0eebe7a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relates: #5879
Preview: https://github.com/vecil/flux2/blob/docs/propose-rfc-0014-advanced-dependency-management/rfcs/xxxx-advanced-dependency-management/README.md
This proposes an RFC that defines how Applier controllers (Kustomization, HelmRelease) could handle multi-hop dependencies on arbitrary resource kinds, including cross-namespace and cluster-scoped resources, with support for implicit (kstatus-based), explicit (user-defined CEL expressions), and existence-only dependency checks, while also proposing to unify the Applier and ResourceSet APIs around dependency management.
The document clarifies each design choice alongside already-debated alternatives, noting backward-compatibility throughout and surfacing caveats (e.g. interactions between kstatus-based built-in checks and resources lacking a
Readycondition) with proposed mitigations for each.