If you use Kubernetes in production, you should already know that monitoring and logging solutions are essentials if you want to make sure that your cluster is healthy at all times. Lack of computing resources and capacity misconfigurations are one of the most common causes of failed deployments. Especially if you are an operator, you always need to know the load of your cluster in order to perform capacity planning and setup autoscaling.

There are many articles and videos about practicing Continuous Delivery (CD) with applications, but not nearly as many for infrastructure. The same can be said for GitOps applied to infrastructure. That is a bit strange given that applications and infrastructure are almost the same today. Both are defined as code, and everyone stores code in Git repositories. Hence, GitOps is just as good of a fit for infrastructure as for anything else.

CI and CD tools are popular for a good reason. They help us automate the application lifecycle, fully or partially. However, the problem is that, in some cases, we are moving away from the core principles behind the CI and CD processes. Products on the market tend to “bend” the definitions of what CI and CD are so that their products can get “yet another sticker”. This is an attempt to bring sanity into the insane situation in which everything and nothing are CI and CD.

With the emergence of “Shift Left” as common practice for development, we’re seeing many opportunities to reduce costs around our development practices, but what about security? Prisma Cloud is supporting “Shift Left” by making their scanning capabilities available to Developers and CI Tooling to run scans against microservice projects. As a bonus, the Prisma Cloud product suite scanning capabilities fit perfectly within Codefresh.