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
In my career, I have worked across so many types of companies. (List not in order) * A large tech company * A large non-profit * A small non-profit * An early-stage tech startup * A small boot-strapped Azure and DevOps consultancy * A medium-sized venture-backed Microsoft-focused consultancy * A publicly traded consultancy that focuses on Government
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
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
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.