When I did initial research on these two GitOps tools a couple of years ago, I went through several comparison articles that looked at the key features - often in the form of a table. ...
When deploying infrastructure that includes Kubernetes clusters, there is always a point where we have to decide exactly what resource should be handled via infrastructure code tools like Terraform, and what resources will be managed by Kubernetes itself. ...
Scenario # “You’ll get a Kubernetes environment, please install your app on it. ...
Use case # Though you’d usually assume that a Kubernetes or OpenShift environment would always have a container registry available, this may not always be the case in more restricted or highly secured environments. ...
TL;DR GitOps is king, and once you’ve tried it you can’t go back 👑 ...
Despite reading through the docs on Pulumi Outputs a few times, getting a grasp of how to deal with outputs can be difficult. ...
Purpose # Cloud infrastructure is nice and all, but sometimes you just want a simple kubernetes cluster to play around with as cheaply as possible, taking advantage of some hardware you already have laying around. ...
What is the aws_auth and why does it exist? # Unlike AKS, by default AWS EKS uses AWS authentication tokens for managing access to the cluster. ...
Rationale # Terraform allows you to create all the cloud resources you could want with just a few commands, however it usually is paired with other tools like Ansible to then apply configurations on those resources and bring up applications. ...
See previous article on OAuth2 Proxy configuration with nginx-ingress. ...