Operations | Monitoring | ITSM | DevOps | Cloud

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

Kubernetes monitoring and troubleshooting made simple

Infrastructure monitoring was difficult enough when entire businesses ran off a few bare metal servers in a dusty, forgotten closet. Other IT infrastructure monitoring tools fell short, unable to provide complete and granular-enough metrics in real time, even when we were only dealing with a handful of systems responsible for running every part of the application stack.

Highly available Kubernetes in IoT: MicroK8s on RaspberryPi

Learn how to set up a Pi-Hole instance with a single command and a cluster of Raspberry Pis on MicroK8s. High availability, load balancing and Kubernetes configuration included. The Raspberry Pi 4 brings the graphics, RAM and connectivity needed for a Linux workstation, so why not use a cluster to set up your own Pi-Hole, the open source network-level ad blocker that acts as a DNS sinkhole or DHCP server.

Civo official launch!

Countdown to our official production launch! We'll be giving you a behind the scenes look at how we build and provision a new CivoStack region - our custom Kubernetes platform based on K3s. Including a specially recorded time-lapse build of our latest location. Featuring an introduction from our CEO Mark Boost, and Director of Innovation Dinesh Majrekar who will run you through our zero-touch region configuration.

Securing AWS Fargate workloads: Meeting File Integrity Monitoring (FIM) requirements

Securing AWS Fargate serverless workloads can be tricky as AWS does not provide much detail about the internal workings. After all… it’s not your business, AWS manages the scaling of underlying resources for you. :) While the security and stability of Fargate’s system is an inherent feature, Fargate follows a shared responsibility model, where you still have to take care of securing those parts specific to your application..

Secure container orchestration at the edge

The cloud-native way of building software allows for consistency across developer environments and massive scalability of application deployments. Both these attributes are useful for edge, but create new challenges related to security and resilience. Watch this demo to see how Canonical’s modular technology stack addresses these challenges by using well-known cloud primitives.

AWS Fargate runtime security - Implementing File Integrity Monitoring with Sysdig

Thanks to serverless you can focus on your apps, instead of your infrastructure. Take AWS Fargate as an example. A service where you can deploy containers as Tasks, without worrying what physical machine they run on. However, without access to the host How can you detect suspicious activity? Like, file changes on your Fargate tasks? Sysdig provides runtime detection and response to secure Fargate serverless containers.

Datadog Live Containers - Kubernetes Resources

Datadog Live Containers provides multidimensional, real-time visibility into Kubernetes workloads, from Deployments and ReplicaSets down to individual Containers. Using Datadog's curated metrics, teams can track the health and performance of their Kubernetes resources in the appropriate context and surface critical information about every layer of their Cluster.

Dynamic Service Graph | Tigera - Long

Downtime is expensive and applications are a challenge to troubleshoot across a dynamic, distributed environment consisting of Kubernetes clusters. While development teams and service owners typically understand the microservices they are deploying, it’s often difficult to get a complete, shared view of dependencies and how all the services are communicating with each other across a cluster. Limited observability makes it extremely difficult to troubleshoot end-to-end connectivity issues which can impact application deployment.

Application Layer Observability | Tigera - Long

The majority of operational problems inherent to deploying microservices in a distributed architecture are linked to two areas: networking and observability. At the application layer (Layer 7), the need to understand all aspects associated with service-to-service communication within the cluster becomes paramount. Service-to-service network traffic at this layer is often using HTTP. DevOps teams struggle with these questions: Where is monitoring needed? How can I understand the impact of issues and effectively troubleshoot? And how can I effectively protect application-layer data?