The latest News and Information on Containers, Kubernetes, Docker and related technologies.
“How do I enable GitOps for my network policies?” That is a common question we hear from security teams. Getting started with Kubernetes is relatively simple, but moving production workloads to Kubernetes requires alignment from all stakeholders – developers, platform engineering, network engineering, security. Most security teams already have a high-level security blueprint for their data centers.
Amazon ECS allows you to easily run containers in AWS in units called tasks. Groups of identical tasks are called services, and groups of services running on the same infrastructure are called clusters. Since it is critical to the health of your application, properly monitoring ECS is a top priority for most teams. In this blog post, we will go over how Blue Matador monitors ECS tasks automatically and without configuration.
Over the last few years, we have seen a significant shift with companies moving away from developing heavy, monolithic applications and instead adopting new approaches like microservices and even serverless applications. These allow companies to work in a faster and more agile way. Speed and agility are important when a task like deploying a new piece of code to production multiple times a day is normal behavior for a modern environment.
Windows Support went GA for Kubernetes in version 1.14 and represented years of work. This has been the effort of excellent engineers from companies including Microsoft, Pivotal, VMWare, RedHat, and the now-defunct Apprenda, among others. I’ve been a lurker and occasional contributor to the sig-windows community going back to my days with Apprenda, and I’ve continued to follow it in my current role with Rancher Labs.
With Sumo Logic, we can put all of these pieces together to build end-to-end Observability in Kubernetes.
