This message was deleted.
# azure
a
This message was deleted.
a
Hi, we do 1. It costs the same that it does in AWS, around 1k usd for each client (two clusters, non prod and prod with t3.medium in AWS and equivalent in Azure) using reserved instances, in our case, as a software factory, we pass those costs to the client, so is not an issue on our side 2. We don't integrate with anything really, our infra is done in a way that is the most Cloud agnostic possible (we use external-dns, cert-manager, etc), the only integration is with ExternalSecrets and each cloud provider secret solution 3. We manage low user and low volume apps, this does not apply to us really 4. a. Updates : We update the Kubernetes version in Terragrunt directly, if we need to update Rancher we tear down the VM and recreate it with a newer docker container b. Backups : We backup secrets (that have env variables) and ArgoCD state to S3 or StorageAccounts, with that we can recover a cluster easily Hope it helps!
t
thanks so much!
I have one doubt though. Is t3.medium enough for production RKE2 control plane?
also, how is it 1k USD per month for t3.medium servers? 🤔 2 x 3 control plane servers would be around 200 USD only right? is it 1k including the RKE2 agents too?
a
hi
we usually have 2 clusters for each client, a prod one and a non prod one, so there you have 12 t3.mediums, if you add all the misc stuff used (we deploy everything with private IP and that costs a little bit more) ends up at 1k usd a month
usually t3.medium works for a while, depending on the proyect, that could be 6 months or can be 2 years, that depends on how fast the proyect grows
but is a decent base line for the first year or so
t
yeah, that makes sense. thanks for explaining!
r
If you want use PaaS AKS Services you must use Azure kubernetes distribution, AKS have also autoscaling for node pool. Take no sense use RKE2 in IaaS, what is the benefit?
t
The main aim was consistency - since we are using RKE2 in our on-premise setups, we wanted to see if we can RKE2 in cloud as well. Also, we wanted to be as much cloud agnostic as possible
But, after weighing the pros and cons, we eventually went ahead with AKS in our Azure cloud setup