-
|
The docs say,
Even with the warning enabled, I'm not able to figure out how to do this? The warning appears in the project, and tells me there are orphaned resources, but it doesn't say what those are. It also says you can "inspect/remove" them via the UI, which I'd also like to do. I should also mention the docs state,
And then appear to show an application details page showing an orphaned resource. This makes little semantic sense (orphans are part of a project, not an application, no? The docs themselves even say as much: "Orphaned Kubernetes resource is a top-level namespaced resource which does not belong to any Argo CD Application" — what app's details page am I suppose to even be looking at?), but it also doesn't work: my application details page has the warning, but does not show any orphaned resources. (Relatedly, I'm also not clear on how Argo detects orphans. I would have expected resources managed by Argo to have an annotation to that effect, but they do not. There is |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
One needs to click "Show Orphaned" on the sidebar. I still wonder a bit about the UI here, as these are not logically associated with any application. This seems like Projects should be given a more prominent place in the UI, and orphans are a subset of those. It appears the other answer to my question is that it's any resource in the namespace, with some exceptions noted by the docs. That also explains the rather odd "Orphaned Kubernetes resource is a top-level namespaced resource" — after all, why would an orphan need to be namespaced? One could easily orphan non-namespaced resources. These are more like "unmanaged" — they might have been orphaned, or they might just be outside Argo. (Argo seems to presume here that it owns the NS, which isn't all that unreasonable.) |
Beta Was this translation helpful? Give feedback.
-
|
Fwiw, I have a few tickets to try to improve the experience |
Beta Was this translation helpful? Give feedback.
One needs to click "Show Orphaned" on the sidebar.
I still wonder a bit about the UI here, as these are not logically associated with any application. This seems like Projects should be given a more prominent place in the UI, and orphans are a subset of those.
It appears the other answer to my question is that it's any resource in the namespace, with some exceptions noted by the docs. That also explains the rather odd "Orphaned Kubernetes resource is a top-level namespaced resource" — after all, why would an orphan need to be namespaced? One could easily orphan non-namespaced resources.
These are more like "unmanaged" — they might have been orphaned, or they might just be outside Argo. (A…