The latest News and Information on Containers, Kubernetes, Docker and related technologies.
In case you missed the big news, after almost two years in beta and early access phases, Civo is now general availability! Find out what this means for Civo and the future of the platform over at our blog. We've also launched the first-ever Civo Hackathon! This is an initiative to bring together developers, architects, experts, and students from across the globe to develop innovative Kubernetes projects on Civo.
Helm has some limits, discover how we extended functionnalities with Rust.
In our previous post , we focused on tips for making the transition and migration to Kubernetes a smoother, and less painful process. In this post, we’d like to now provide some tips from the operational trenches for future-proofing your Kubernetes operation, after making the move. Kubernetes, as a software-driven system, has many benefits for engineers and DevOps teams to take advantage of.
Kubernetes has evolved into the leading platform to build your microservices systems. Given its increased maturity over the past few years as well as the robust ecosystem which has been built around its technology, Kubernetes has become more production-ready than ever. Nevertheless, it still has its own unique set of challenges. In particular, it brings a lot of complexity into play with its adoption.
With the Calico 3.10 release, Dynamic Packet Capture is available in Dynamic Service Graph. This means users who require self-service, live troubleshooting for microservices and Kubernetes workloads can capture and evaluate traffic packets on endpoints without writing a single line of code or using any 3rd-party troubleshooting tools. Users don’t need to learn about or have knowledge of kubectl or YAML to troubleshoot their microservices and Kubernetes cluster.
The Telegraf 1.20.3 release changed the official Telegraf DockerHub image to no longer run the Telegraf service as root. With this change, the Telegraf service runs with the least amount of privileges in the container to enhance security given the wide extensibility and array of plugins available in Telegraf.
KubeCon/CloudNativeCon North America 2021 was a whirlwind of sessions, talks, panels, bonding, and learning. As it was a hybrid event, Civo was represented both in person at a booth that featured Sophia and David from our North American team, as well as virtually through our online booth and talks. Plus, we made an announcement of the General Availability of Civo Kubernetes at the event!
Monitoring cloud-native systems is hard. You’ve got highly distributed apps spanning tens and hundreds of nodes, services and instances. You’ve got additional layers and dimensions—not just bare metal and OS, but also node, pod, namespace, deployment version, Kubernetes’ control plane and more. To make things more interesting, any typical system these days uses many third-party frameworks, whether open source or cloud services.
