Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Containers, Kubernetes, Docker and related technologies.

Configuring Amazon SNS for CloudWatch Alarms

In this video Blue Matador will walk you through how to set up Amazon SNS to receive CloudWatch alarms by email or text message. Using AWS CloudWatch isn't hard, it's just tedious with an unusable UI. We are experts in AWS and Kubernetes monitoring and have built Blue Matador to make the lives of DevOps professionals easier. Learn more about our cloud monitoring solution and other CloudWatch resources at www.bluematador.com.

Blue Matador Helps Canopy Monitor AWS and Kubernetes Proactively

Before Blue Matador Canopy was mostly using CloudWatch to monitor their AWS and Kubernetes infrastructure. Things they didn't know they should monitor would break. Now, they have moved from being proactive rather than reactive and are monitoring all of the unknowns. Find out more at www.bluematador.com

Monitor Twistlock with Datadog

Twistlock is a platform for managing security and compliance within various environments, including virtual machines, containers, and serverless functions. Ensuring legal and technical security is just as valuable as preventing outages and errors, which is why Datadog is delighted to announce a new integration with Twistlock. With this integration, you can track security and compliance risks within the same platform as the metrics, traces, and logs you already collect with Datadog.

7 Key Considerations for Kubernetes in Production

Today Enterprise IT does not question the value of containerized applications anymore. Given the move to adopting DevOps and cloud native architectures, it is critical to leverage container capabilities in order to enable digital transformation. Google’s Kubernetes (K8s), an open source container orchestration system, has become the de facto standard — and the key enabler — for cloud native applications, and the way they are architected, composed, deployed, and managed.

Comparing kube-proxy modes: iptables or IPVS?

kube-proxy is a key component of any Kubernetes deployment. Its role is to load-balance traffic that is destined for services (via cluster IPs and node ports) to the correct backend pods. Kube-proxy can run in one of three modes, each implemented with different data plane technologies: userspace, iptables, or IPVS. The userspace mode is very old, slow, and definitely not recommended! But how should you weigh up whether to go with iptables or IPVS mode?