-
Notifications
You must be signed in to change notification settings - Fork 44
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
Custom Resource Object Don't Show Up in ArgoUI #26
Comments
Please let me know if you could also display cluster-scoped objects with Argo CD. We had this request before, but it turned out to be ArgoCD didn't have this capability. |
I see. Thank you. I'll check into that and post back. |
So, I checked and CRDs (which are cluster scoped) show up perfectly fine in the UI. Also I saw that issue if once present seems fixed. argoproj/argo-cd#10314 |
Further, the objects (clusterissuers) in this case don't seem to get the annotations required to track them. Though adding said annotations doesn't seem to help either. |
ping @reedjosh |
I have a Helm chart that only installs ClusterIssuers. A set of Custom Resource Objects.
Flux does a great job of installing the objects, but the Helm Release objects do not show up in the ArgoUI.
Combining this with: #16, it seems that using FSA where Argo is the front end and Flux is the back, just doesn't seem to work great.
As of right now I'm guessing this is because the Flamingo patches don't handle CRDs and their respective objects?
I see that the status field of an argo application is where objects are tracked.
The text was updated successfully, but these errors were encountered: