terraform
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,
Azure Kubernetes Service
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
terraform
I admit it. There was a time, very recently, when I deployed infrastructure by going into the Azure portal and clicking some buttons. It seems so easy! But there's an associated cost. So much so that I just finished defined and deployed a new Azure Kubernetes Service cluster
Azure Kubernetes Service
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.
Azure Kubernetes Service
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
Kubernetes
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
ci/cd
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
GitOps
Simply put: GitOps is a way of managing infrastructure, configuration, permissions, etc... in an explicit and repeatable way by simply pushing changes to git and allowing an associated pipeline to make the changes come to life. Let's dig a little deeper. What GitOps Isn't GitOps is
terraform
If you have a need to quickly spin up AKS clusters on a regular basis, this GitHub repo can serve as a nice scaffold: https://github.com/justin-vanwinkle/terraform-k8s It has everything you'll need to get going: * A Terraform config that defines a Kubernetes cluster with autoscaling nodes