What would you like to be added?
Fine-Grained Kubernetes Resource Dependency Analysis
Why is this needed?
Kusion initially used ordered kinds to determine the dependency order between Kubernetes resources. This PR changed the chain dependency model to a graph-based dependency model, but it still does not meet our requirements.
The issue is that dependency based on resource kinds cannot fully capture all scenarios. For example, a Deployment may use a ConfigMap, but an unreferenced ConfigMap might still be marked as a dependency of the Deployment, preventing the deletion of the isolated, unreferenced ConfigMap.
Therefore, we need a method that can analyze true resource-level dependencies directly from the spec, rather than relying on coarse-grained kind-based dependencies.
Related Issues and Prs(Let's handle these problems in one way!)
issues:
#511
#1402
#1404
prs:
#1406
KusionStack/kusion-module-framework#41
What would you like to be added?
Fine-Grained Kubernetes Resource Dependency Analysis
Why is this needed?
Kusion initially used ordered kinds to determine the dependency order between Kubernetes resources. This PR changed the chain dependency model to a graph-based dependency model, but it still does not meet our requirements.
The issue is that dependency based on resource kinds cannot fully capture all scenarios. For example, a Deployment may use a ConfigMap, but an unreferenced ConfigMap might still be marked as a dependency of the Deployment, preventing the deletion of the isolated, unreferenced ConfigMap.
Therefore, we need a method that can analyze true resource-level dependencies directly from the spec, rather than relying on coarse-grained kind-based dependencies.
Related Issues and Prs(Let's handle these problems in one way!)
issues:
#511
#1402
#1404
prs:
#1406
KusionStack/kusion-module-framework#41