In this article, we will look into common ways to secure secrets in a Kubernetes application and how to manage them in a GitOps workflow based on ArgoCD with the help of Sops
The problem is the following: your application depends on some secrets that you need to store securely and make available to your running application.
You can address this requirement in two ways:
Kubernetes clusters are not exactly cheap, can be complex to set up, and operate properly. For this reason, you may be tempted to reserve “true” online Kubernetes clusters for running your production workloads and have clusters running locally for development purposes.
In this post, we will explore different ways to easily set up a local Kubernetes cluster and the associated trade-offs that accompany them.
Different solutions exist to run a Kubernetes cluster on your laptop. Let’s review a few of these.
Minikube is the solution the Kubernetes project documentation advises you to use. It deploys a VM with a single node cluster. You pay the price of virtualization, as seen in the minimum requirements for the host machine (2 CPU, 2 Go RAM, 20 Gb…
Options for creating an EKS clusters are many, amongst others:
Of course, these solutions are giving you quite a bare cluster and the challenge is then to add all the tools to be production-ready.
One desirable feature is the ability for the cluster to autoscale depending on the workload. More precisely, when additional load is applied, we are looking to horizontally scale our cluster by increasing the number of nodes.
In this post, we will set up a new cluster from scratch using CDK and take a look at the Cluster Autoscaler component to fulfill this requirement. …