-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: namespaced resources owned by cluster scoped resources don't show up in the UI #8222
base: master
Are you sure you want to change the base?
Changes from all commits
c1ddd02
921523b
78e49f2
539a7c6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1150,7 +1150,7 @@ export const ApplicationResourceTree = (props: ApplicationResourceTreeProps) => | |
if (treeNodeKey(child) === treeNodeKey(root)) { | ||
return; | ||
} | ||
if (node.namespace === child.namespace) { | ||
if (node.namespace === child.namespace || node.namespace === undefined) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi @chetan-rns, help me to understand why/when the node namespace will be undefined as opposed to default? This part sets the edges (lines) between 'parent' nodes and the child nodes. So if the child node's namespace is defined OR undefined, then there will be lines connecting to them all. Is this intentional? |
||
graph.setEdge(treeNodeKey(node), treeNodeKey(child), {colors}); | ||
} | ||
processNode(child, root, colors); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just wondering if we need to check the namespace of the resource being allowed by the AppProject of the owning application? While a namespace-scoped object only refers to an owner in the same namespace, this check was not required. But a cluster-scoped owner can be referred to from any namespace, and the application managing the owner might not have access to those namespaces.
Would it be wise to display the dependents in non-allowed namespaces then?