feat(api): allow dependencies on any Kubernetes resource#1653
Open
vecil wants to merge 1 commit into
Open
Conversation
Member
|
Curious in what world this is a refactor? 😅 |
Author
You’re definitely right, I treated the added fields as a non-breaking refactor, but they do change the contract. I apologize for the misclassification. |
vecil
changed the title
vecil
force-pushed
the
refactor/allow-dependencies-on-any-k8s-resource
branch
from
a87d6d4 to
1a488be
Compare
Kustomizations can now depend on any Kubernetes object, improving flexibility in release ordering and readiness behavior. Signed-off-by: Vincent Dely <vincent.dely@ik.me>
vecil
force-pushed
the
refactor/allow-dependencies-on-any-k8s-resource
branch
from
1a488be to
794e447
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
2 participants
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.
Summary
Kustomizationscan now depend on any Kubernetes object, improving flexibility in ordering and readiness handling.Dependencies can reference arbitrary Kubernetes resources and are considered satisfied based on either existence or readiness (via the
readyfield). Defaults are applied during reconciliation forKustomizationentries to ensure backward compatibility.Changes include:
DependencyReferencewith optionalapiVersion,kind, andreadyfieldsfluxcd/cli-utils/pkg/kstatus/statuspackage for readiness evaluation of referenced resourcesRelates fluxcd/flux2#5879