Operations | Monitoring | ITSM | DevOps | Cloud

For those of you who don’t know me, I’m Eric Amodio, creator of GitLens. I’m an innovator, leader, architect, and seasoned full-stack developer. I started developing GitLens way back in 2016 when I fell in love with Visual Studio Code and wanted to play with what was then newly released extension support. It all started with a simple question: could I add Git insights via CodeLens (hence GitLens) to any document? Which of course was yes, and a whole lot more.

Infrastructure as Code (IaC) is the practice of recording the desired state of your infrastructure using a declarative language. In this article, I’m going to assume that your team is starting from scratch. Maybe some of your build process has been scripted, and maybe there is some manual testing and quality assurance work happening. Many readers will find that they are midway through the IaC adoption journey I’ll describe, or that they have missed some steps.

Flux is a CNCF based open source stack of tools. Flux focuses on making it possible to keep Kubernetes clusters and cloud-native applications in sync with external resources and definitions hosted in environments such as GitHub. Implementing tools like FluxCD should enable you to achieve results such as: The results above can bring obvious benefits, and many teams are adopting FluxCD as their tool of choice for GitOps.

The recent contexts have shown that enterprises needed to take a different approach regarding their digital transformation and its prioritisation. They’ve experienced the need to run new configurations and operations remotely on their infrastructure. This quickly showed the benefits of automation solutions to run those changes from few central locations, which highly facilitated the task of systems and network admins.

Bare metal Kubernetes (K8s) is now easier than ever. Spectro Cloud has recently posted an article about integrating Kubernetes with MAAS (Metal-as-a-Service. In the article, they describe how they have created a provider for the Kubernetes Cluster API for Canonical MAAS (Metal-as-a-Service). This blog describes briefly the benefits of bare metal K8s, the challenges it presents, and how the work by Saad Malik and the team from Spectro Cloud solves those challenges.

Today, many of the internet’s busiest websites and applications rely on NGINX to run smoothly. And many of those websites and apps are run as cloud-native services in Kubernetes. In particular, the NGINX Ingress Controller is a best-in-class traffic management solution for cloud‑native apps in Kubernetes and containerized environments that uses NGINX as a reverse proxy, load balancer, API gateway, cache, or web application firewall.