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 👑
...
This post discusses some basic AWS “well-architected” framework principles around networking, and how much idle costs you may be facing when configuring your infrastructure this way.
...
Popup messages that animate nicely and can be dismissed with a click
...
TL;DR # Coming from Kubernetes, my expectations were high for ECS + Fargate to be an “easy way” to deploy stuff.
...
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.
...
This article is inspired by the fantastic post by Avinash Vallarapu on a detailed comparison and performance benchmark between Aurora PostgreSQL and RDS PostgreSQL.
...