Operations | Monitoring | ITSM | DevOps | Cloud

For our second community meetup we focussed on using Civo for CI/CD through GitOps and Github actions for cloud native application development This installment featured talks from our CTO Andy, our Developer Advocate Kai, and guest talks from community members Sam Weston and Johannes Tegnér. The talks touched on a wide variety of topics within CI/CD, from automating builds to monitoring and observability. Here's what was on the agenda...

Interviewing for a new job and finding your right fit is tough enough, not to mention the added stress of interviewing during the COVID-19 pandemic. As stated on our Careers Page, our process is pretty consolidated and we move quickly (you have to when you’re a growing tech company).

If you know anything about WebAssembly (WASM), it’s probably that WASM lets you execute code compiled from languages such as C, C++, Rust, or others in the browser at almost native speeds. You might be less familiar with the fact that WASM is not only an interesting technology in the browser, but also in other environments that require fast sandboxing. As such, WASM has found some popularity with edge computing and as a lightweight docker replacement for certain situations.

In the pre-Kubernetes, pre-container world, backup and recovery solutions were generally implemented at the virtual machine (VM) level. That works for traditional applications when an application runs on a single VM. But when applications are containerized and managed with an orchestrator like Kubernetes, this system falls apart. That means effective disaster recovery (DR) plans for Kubernetes must be designed for containerized architectures and natively understand the way Kubernetes functions.

Being in the DevOps space, we're often asked questions about software deployment like, "What's the difference between continuous deployment and continuous delivery?", "What is continuous deployment?", and "Are continuous deployment and continuous delivery the same thing?" So first, let's start by clearly defining these terms.

In the world of containers and Kubernetes, observability is crucial. Cluster administrators need visibility into the infrastructure and cluster operators need to know the status of their workloads at any given time. And in both cases, they need observability into moving objects. This is where Metricbeat and its autodiscover feature do the hard part for you.

Another year of empowering DevOps teams has passed and what a year it’s been! I’d like to take a moment to reflect on the journey, the milestones and challenges this past year encompassed. The last year has been our most transformational to date. We’ve had a huge amount of ups and downs and I’m incredibly proud to say that we got through it and our organization is more resilient, more aligned in our vision and closer as a result.