The latest News and Information on Containers, Kubernetes, Docker and related technologies.
Welcome to the Civo update for July 2021. In this edition we unveil some of the data from our Kubernetes in 2021 developer survey, a sneak peek at GitHub Copilot, and a case study on how Civo and StorageOS combine to provide cloud native storage for our Kubernetes platform.
When we launched Qovery in January 2020, our product was only supporting app deployment on Amazon Web Services (AWS). 20 months later, 5534 developers from more than 120 countries use Qovery to deploy their apps on AWS and Digital Ocean. Today, more and more European companies would love to benefits from the excellent user experience of Qovery on a European cloud service provider 🇪🇺.
We’re constantly told to “Shift Left” and that Secure DevOps is the only way to have confidence in your cloud native applications. But speaking to end-users and industry colleagues, it’s clear that there are some major challenges in adopting Secure DevOps. If we read our history books, we know that DevOps wasn’t successfully adopted by buying tools, and a true cultural movement towards DevOps wasn’t established by having a small dedicated team of DevOps specialists.
Every developer knows there are some utilities that are completely indispensable from their workflows. The programmer’s toolbelt, if you will. These toolbelts are usually different from person to person, but if there is one tool that everyone should use or at least know how to use, it is tcpdump. If you are unfamiliar, tcpdump is a tool that allows you to dump and inspect live network traffic being observed on a network interface.
Sometimes the best way to understand something is to take it apart and see how it works. This blog post will help you take the lid off your Calico eBPF data plane based Kubernetes cluster and see how the forwarding is actually happening. The bonus is, unlike home repairs, you don’t even have to try to figure out how to put it back together again! The target audience for this post is users who are already running a cluster with the eBPF data plane, either as a proof-of-concept or in production.
In this blog post, I will be looking at 10 best practices for Kubernetes security policy design. Application modernization is a strategic initiative that changes the way enterprises are doing business. The journey requires a significant investment in people, processes, and technology in order to achieve the desired business outcomes of accelerating the pace of innovation, optimizing cost, and improving an enterprise’s overall security posture.
Current observability practice is largely based on manual instrumentation, which requires adding code in relevant points in the user’s business logic code to generate telemetry data. This can become quite burdensome and create a barrier to entry for many wishing to implement observability in their environment. This is especially true in Kubernetes environments and microservices architecture.
Ever since Google made Kubernetes open-source in 2014, it has enjoyed incredible growth, helping businesses of all sizes to successfully manage their containers and ultimately make the most of all that our cloud native world has to offer. Individual users certainly initially led the charge with Kubernetes, identifying issues, and generally exploring the best ways to intelligently test, manage, and deploy workloads.
A couple of days ago, I was pleasantly surprised to suddenly see a tweet come in from Viktor Farcic. Viktor now works at upbound.io who developed Crossplane, and he also runs his own popular YouTube channel and co-hosts DevOps Paradox podcast. He’s well respected in the cloud native community. When I saw the tweet and noticed that Viktor had recorded a review of Civo on YouTube, I was just hoping he was kind to us...and I am pleased to say he was!
I am super excited to announce that we released the support of Environment Variables and Secrets. Watch the video to see those features in action. Environment Variables and Secrets are similar. The main difference is that the Secrets are encrypted and the value can’t be revealed. Both are injected at the build and runtime of your applications. Give it a try now! Resources: I am eager to have your feedback. Put a comment here.
