Kubernetes is everywhere! In the public and private cloud, and from the enterprise to startups, the majority of IT executives around the world have explored Kubernetes, and how it has evolved the way many organisations are developing and deploying their applications. But what is scary about it, and how can organisations better leverage one of the greatest tools in the field while overcoming the biggest challenges facing CIOs when adopting Kubernetes?

In this blog post, I will be talking about label standard and best practices for Kubernetes security. This is a common area where I see organizations struggle to define the set of labels required to meet their security requirements. My advice is to always start with a hierarchical security design that is capable of achieving your enterprise security and compliance requirements, then define your label standard in alignment with your design.

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.

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!

Kubernetes is a game-changing technological advancement, enabling infrastructure and operations teams to automate application deployment and management at scale. But it has also presented new challenges to developers. As organizations adopt cloud native application paradigms, they face a developer experience crisis due to the complexity of the cloud native ecosystem and a steep learning curve for developing applications for Kubernetes.

Heaven knows we all could use some luck these days, and observability may be just the thing we need. But observability isn’t luck, and it isn’t really new either. A few people even know that observability is an aspect of control theory, which dates back to the 1800s! In this blog post, I’ll cover some of the history of observability vs.

October marks the five-year anniversary of Calico Open Source, the most widely adopted solution for container networking and security. Calico Open Source was born out of Project Calico, an open-source project with an active development and user community, and has grown to power 1.5M+ nodes daily across 166 countries. When Calico was introduced 5 years ago, the world—and technology—was much different from what it is today.

How are organizations managing security and compliance for open source packages nowadays? As you may recall from our annual State of Kubernetes surveys, security and compliance are always a top concern. Our recent survey, The State of the Software Supply Chain: Open Source Edition 2021, gives some great insight into how people are addressing those concerns. It also gives some guidance on how to build your own policies.

I am super excited to announce that we have released our "clone environment" feature. It is a massive update!! With one click, you can duplicate an existing environment. The cloning environment has been a significant feature expected by our customers and users for a long time. Thanks to our beta testers and our team for making it live for everyone. Here is a short video showing the clone environment in action ‍

As Kubernetes Pods don't store data persistently, it offers different storage components to prevent this data loss. In this blog, learn how Volume works in Kubernetes, how to create it, and how to attach it to the Pod. Before exploring Kubernetes volumes, let’s first understand Docker. Docker containers are meant to be transient, which means they will only last for a short period. They are called upon when required to process data and are destroyed once finished.