production first - Kubernet

Kubernet

Sign in Subscribe

production first

A collection of 8 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.

Choosing a Git Branching Strategy

Choosing a Git Branching Strategy

There are several out there, and a lot of opinions to go with them. Having served in a consulting capacity for many organizations, ranging from small startups to very large enterprises, I have seen all of the major strategies. I've even seen organizations make up their own strategies in an

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

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

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

Starting with Production

Starting with Production

Too many times, I have worked with clients where the client demands that we create a new system starting with a development environment. From there, they often want to create additional environments in front of production. QA, UAT and Staging perhaps. Then comes production. Unfortunately, this approach is a fallacy.