It finally happened. At the start of DockerCon Europe and a week before KubeCon was set to take place in the U.S., researchers discovered the first major vulnerability within Kubernetes, the popular cloud container orchestration system.
This is our final installment of our series on the Collaboration Hierarchy. Last week, we looked at Conscious Communication Channels. This week, we will be discussing how to accelerate feedback loops and knowledge sharing to get the most out of your collaborative culture.
A decade ago, an enterprise adopting DevOps was a rare event. In the last decade, some businesses dipped their toes in, others spent big money going all in. Now the question isn’t whether to make the culture shift, but how to be successful as it grows.
Security and compliance are different disciplines that share a common foundation of risk and control. They aim to minimize the risk to the company by ensuring that the proper controls are in place.
Container security orchestration allows to define within your security policy how you are going to respond to your different container security incidents. These responses can be automated in what is called security playbooks.
While you’re likely familiar with role-based access control, Sysdig teams introduce the concept of service-based access control.
Apache ActiveMQ is message-oriented middleware (MOM), a category of software that sends messages between applications.
In Part 1 of this series, we looked at how ActiveMQ works, and the key metrics you can monitor to ensure proper performance of your messaging infrastructure. In this post, we’ll show you some of the tools that you can use to collect ActiveMQ metrics.
