Each time ArgoCD tries to deploy our development environment to the Kubernetes cluster, the cluster is instructed to check the security posture of incoming Kubernetes manifests with the Bridgecrew admission controller.
Details of all the issues found with the development deployment can be seen in this view, with filters for severity, tags, and other important attributes.
We’ve detected 17 issues on our Deployment object and no issues on the service object. This explains why the service object was successfully deployed to the Kubernetes cluster, but the Deployment was not.
At the bottom of each flagged item, we’ll see more information aboutthe security issue that prevented a successful deployment to the cluster.
In this example, one issue we see is that we have no securityContext settings on our pods or containers within the Deployment.
We can bring up more information and guidance on the issue with the lightbulb symbol on the issue’s header.
Guidelines (like this page) provide more detail and context for each issue.