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

Ability to generate a warn/alert when a namespace deviates from the expected state #1167

Closed
edlee2121 opened this issue Feb 23, 2019 · 6 comments · Fixed by #2188
Closed
Assignees
Labels
enhancement New feature or request security Security related
Projects
Milestone

Comments

@edlee2121
Copy link
Contributor

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.

@stale
Copy link

stale bot commented Apr 24, 2019

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.

@stale stale bot added the wontfix This will not be worked on label Apr 24, 2019
@alexmt alexmt removed the wontfix This will not be worked on label Apr 24, 2019
@alexec
Copy link
Contributor

alexec commented Apr 24, 2019

#1480

@alexec alexec added enhancement New feature or request cluster management labels Jun 14, 2019
@edlee2121 edlee2121 added the security Security related label Jul 20, 2019
@edlee2121 edlee2121 added this to the v1.2 milestone Jul 20, 2019
@edlee2121
Copy link
Contributor Author

Please prioritize for the next release.

@alexec
Copy link
Contributor

alexec commented Jul 22, 2019

I think it's a bit late for v1.2, Can we push back to v1.3?

@edlee2121
Copy link
Contributor Author

v1.3 is fine

@alexec alexec modified the milestones: v1.2, v1.3 Jul 22, 2019
@alexec alexec added security Security related and removed security Security related labels Jul 23, 2019
@alexec
Copy link
Contributor

alexec commented Jul 23, 2019

See #1479

alexmt pushed a commit to alexmt/argo-cd that referenced this issue Aug 5, 2019
@alexec alexec added this to To do in 2019-08-05 (previous) via automation Aug 6, 2019
@alexec alexec moved this from To do to In progress in 2019-08-05 (previous) Aug 6, 2019
@alexmt alexmt moved this from In progress to Review in progress in 2019-08-05 (previous) Aug 6, 2019
@alexmt alexmt moved this from Review in progress to In progress in 2019-08-05 (previous) Aug 6, 2019
alexmt pushed a commit to alexmt/argo-cd that referenced this issue Aug 9, 2019
@alexec alexec removed this from In progress in 2019-08-05 (previous) Aug 14, 2019
@alexec alexec added this to To do in 2019-08-14 via automation Aug 14, 2019
@alexec alexec moved this from To do to In progress in 2019-08-14 Aug 14, 2019
alexmt pushed a commit to alexmt/argo-cd that referenced this issue Aug 19, 2019
alexec pushed a commit that referenced this issue Aug 19, 2019
alexmt pushed a commit to alexmt/argo-cd 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 to alexmt/argo-cd that referenced this issue Aug 22, 2019
2019-08-14 automation moved this from In progress to Done Aug 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request security Security related
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants