pipelines as code - Kubernet

pipelines as code

A collection of 9 posts

Terraform and Helm

Terraform and Helm

Did you know that you can fully create a managed Kubernetes cluster in Azure using Terraform? Well you can take that one step further and also manage what's installed in your cluster using Terraform and Helm. This can be done by using the Helm provider for Terraform. Now, let's say

How to Make your Developers Work Faster

How to Make your Developers Work Faster

Find the courage to slow down so you can speed up. This counterintuitive approach is indubitably the most effective way to create a high-performing team or organization.

How Many Kubernetes Clusters You Should Have 🚢

Azure Kubernetes Service

How Many Kubernetes Clusters You Should Have 🚢

At my current company, the powers that be have bought into a multi-cluster approach. I'm not saying 1 cluster per environment or region. No. I'm saying 1 non-production and 1 production cluster per system per region. Essentially, each team gets their own pair of clusters in each region we choose

Pipelines as Code - Don't Reinvent the Wheel

Pipelines as Code - Don't Reinvent the Wheel

The term "Pipelines as Code" means that you are defining the process through which your code moves from source control, all the way to running in production. This practice is absolutely necessary if you want to build a high performing development process that allows your system to be rapidly iterated

GitOps with Terraform for Kubernetes

Azure Kubernetes Service

GitOps with Terraform for Kubernetes

Did you know that Terraform can run kubectl commands? Yep! There's a provider for Kubernetes. The Kubernetes provider has a growing list of resources that you can manage via Terraform. For instance, you could declaratively and explicitly manage Kubernetes permissions via Terraform by defining roles and role bindings. Then when

How to Fix Terraform Helm and Kubernetes Providers after implementing AAD RBAC in AKS

Azure Kubernetes Service

How to Fix Terraform Helm and Kubernetes Providers after implementing AAD RBAC in AKS

I implemented the Azure Active Directory (AAD) integration with Azure Kubernetes Service (AKS) for Role Based Access Control (RBAC) today in an existing cluster. I use Terraform to manage the cluster as well as all of the Helm installs and custom resource definitions that I apply via kubectl. The Problem

Migrating to Kubernetes: A Manager's Guide to Effective Transition (Part 1)

Migrating to Kubernetes: A Manager's Guide to Effective Transition (Part 1)

For teams that are looking to build out a Kubernetes cluster and migrate their applications, my first reaction is always the same, no matter the skill-level and capability of the team. Here's something of how the conversation goes: First, let's identify your Kubernetes administrators and let them begin building out

CI/CD for Kubernetes Applications (Part 1)

CI/CD for Kubernetes Applications (Part 1)

So you're ready to automate your application deployment to Kubernetes. You've made the right choice! Let's consider what a pipeline might look like if you are using Kubernetes manifests directly without the use of a tool such as Helm. In other words, you just have some YAML files sitting somewhere

GitHub Actions - Build and Push a Docker Image

GitHub Actions - Build and Push a Docker Image

Github Actions are here, and they are really great to work with. Let's take a look at how you would use a GitHub action to build and push a Docker image to your GitHub container registry. First, here's the YAML file we will consider. It lives in a repository at