Open erdii opened 1 year ago
Hi @erdii! Really glad that you found this tool useful for you & thanks for writing this comprehensive bug report 🙏
Can I also trouble you to share the example outputs shared above but including the --output=wide
flag? That would help me get a better idea of the list of relationships that the tool as resolved from scanning through all the resources fetched from your cluster.
I'll try to make some time to take a good look at this soon 🙏
Hey @tohjustin :wave: :) I think I've experienced a bug and hope this report helps improving your wonderful tool. Please let me know if you want more info or something else!
Story time
I've installed package-operator which brings its own CRDs which are strictly organized in a hierarchy.
After installation of the operator [1], there is a tree of objects, glued together by
ownerReferences
that looks like this:But some object relations are missing from kubectl-lineage's output. This is the output for
kubectl lineage clusterpackage package-operator
:I know that there is a missing ServiceAccount which I can reverse query for its dependencies with
kubectl lineage -D -n package-operator-system ServiceAccount/package-operator
:and also a deployment
kubectl lineage -D -n package-operator-system Deployment/package-operator-manager
:I'll link the
Package
sources for reference [2]. The full list of missing dependent objects should be:All objects have proper
ownerReferences
set up. I've tried to include all relevant object manifest in the attached dump. [3][1]
[2] https://github.com/package-operator/package-operator/tree/v1.6.6/config/packages/package-operator [3] package-operator-objectdump.tar.gz