github
GitHub has taken a strong stance on not implementing a folder structures to support sorting of repositories. Why is that? They believe that it is unnecessary – and it is. Adding folders would add a layer of confusion that can be solved easily at a more meta level. This holds true
git
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
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.
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
github
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
ghost
Let's get right down to business: Can Ghost CMS run in Kubernetes? Yes! This site is proof. It's running on my personal cluster in Digital Ocean (previously Azure Kubernetes Service, but Digital Ocean costs about half the price). How to do it It's relatively
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