Skip to content
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

Migration document recommends using the argocd namespace which loses monitoring #331

Open
gnunn1 opened this issue Jun 16, 2022 · 0 comments
Assignees

Comments

@gnunn1
Copy link
Collaborator

gnunn1 commented Jun 16, 2022

The migration document (https://github.com/redhat-developer/gitops-operator/blob/master/docs/Migration_Guide.md) recommends sticking with the argocd namespace instead of migrating to the openshift-gitops namespace. While this is certainly convenient for existing users of community argo the downside is that AFAIK cluster monitoring will not pick up the argocd namespace since it only monitors openshift-* namespaces like openshift-gitops.

As a result customers lose out on alerting for out of sync applications and general monitoring of the instance. It is possible to deploy the user workload monitoring stack which should pick this up but it is a separate, parallel monitoring stack that is not installed by default. I'm also not sure if the user workload monitoring will trigger the included alert for openshift-gitops?

If my reasoning is correct should we include a note about this in the migration document?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants