Okay, you've moved your infrastructure provisioning from visiting the console page and now adopted IaC ( Infrastructure as Code) for provisioning your infrastructure using Terraform.
So along the way, you discovered that you will need some sensitive credentials like GitHub token to use with aws amplify, datadog API and key deployments?
So you've moved your organization's secret management process to Hashicorp Vault on Kubernetes? everything is working well, but you are about to promote to production, this brings a lot of questions about stability, recovery and fully operational vault servicing your deployments.
You are finding ways to autoscale up and down your nodes in the Kubernetes cluster, and figuring out which autoscaler is the best can be hard since there are many options, which one should you go for?
Well, I would advise going for Karpenter instead of the native Cluster Autoscaler, both projects are sponsored by the AWS team though, but Karpenter is fast when it comes to scaling up and scaling down the nodes.
There are many tools for handling complex architecture of deploying changes of your applications from the build stage to your cluster, most times the term and process of archiving this is called GitOps only if GitHub is being used as the single source of truth in the scenario.
when it comes to containerized environment graceful shutdown, process management and reducing attack surface, I believe we can't leave dumb-init out of it.
When you are preparing your vault environment for production, you would want to implement the end-to-end tls setup as stated in the hashicorp vault production-ready documentation.
Setting resource quotas such as CPU and memory limits/requests is easier said than done.
But why do you need this in the first place?
hello everyone, okay, so I did something recently with GitHub action, re-wrote and optimized a workflow of 900+ lines back to 200+
Hii 馃憢, I am sure you want peace of mind too, haha
Well, there is no way you would be discussing container supply chain security without talking about the signing of container images.
You probably handling your manifest and deployment secrets in kube like this