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
Ability to generate a warn/alert when a namespace deviates from the expected state #1167
Labels
Projects
Milestone
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Please prioritize for the next release. |
I think it's a bit late for v1.2, Can we push back to v1.3? |
v1.3 is fine |
See #1479 |
alexmt
pushed a commit
to alexmt/argo-cd
that referenced
this issue
Aug 9, 2019
alexmt
pushed a commit
that referenced
this issue
Aug 19, 2019
alexmt
pushed a commit
to alexmt/argo-cd
that referenced
this issue
Aug 19, 2019
…ning if app has no orphaned resources
alexec
pushed a commit
that referenced
this issue
Aug 19, 2019
…app has no orphaned resources (#2169)
alexmt
pushed a commit
to alexmt/argo-cd
that referenced
this issue
Aug 20, 2019
alexmt
pushed a commit
that referenced
this issue
Aug 20, 2019
alexmt
pushed a commit
to alexmt/argo-cd
that referenced
this issue
Aug 21, 2019
alexmt
pushed a commit
that referenced
this issue
Aug 21, 2019
alexmt
pushed a commit
to alexmt/argo-cd
that referenced
this issue
Aug 22, 2019
alexmt
pushed a commit
that referenced
this issue
Aug 22, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be a useful security feature if we can warn/alert when a namespace deviates from the expected state. E.g. there is a pod that shouldn't be running based on the deployment manifests.
The text was updated successfully, but these errors were encountered: