Autoscale Kubernetes workloads on any cloud using any event
1–10 of 46 posts
Re: Autoscale Kubernetes workloads on any cloud using any event
#2Re: Autoscale Kubernetes workloads on any cloud using any event
#3Re: Autoscale Kubernetes workloads on any cloud using any event
#4kubernetes is dying, isn't it?
Re: Autoscale Kubernetes workloads on any cloud using any event
#5kubernetes is dying, isn't it?
Re: Autoscale Kubernetes workloads on any cloud using any event
#6Re: Autoscale Kubernetes workloads on any cloud using any event
#7If you have the hardware resources, why not just scale up from the beginning on? If you do not have the resources, you need a lot of money anyways to pay the upscaled rent afterwards.
Re: Autoscale Kubernetes workloads on any cloud using any event
#8Who needs autoscaling? I mean this as a serious question. Has somebody a real story where autoscaling helped out the company or product? If you have the hardware resources, why not just scale up from the beginning on? If you do not have the resources, you need a lot of money anyways to pay the upscaled rent afterwards.
2. Hopefully, if you scale up, you can also scale down, which will save you money when you don't need to rent the resources.
Re: Autoscale Kubernetes workloads on any cloud using any event
#9Who needs autoscaling? I mean this as a serious question. Has somebody a real story where autoscaling helped out the company or product? If you have the hardware resources, why not just scale up from the beginning on? If you do not have the resources, you need a lot of money anyways to pay the upscaled rent afterwards.
Re: Autoscale Kubernetes workloads on any cloud using any event
#10Who needs autoscaling? I mean this as a serious question. Has somebody a real story where autoscaling helped out the company or product? If you have the hardware resources, why not just scale up from the beginning on? If you do not have the resources, you need a lot of money anyways to pay the upscaled rent afterwards.
That said, you could conceivably live at a higher abstraction.
Take dev environments for example. Ideally the team working on infra problems does not need to care how many versions of a backend are operating on the dev environment.
The only thing infra needs to take into account the requested resources.
Perverse incentives on wasting resources aside, it's nice when you can have fewer variables in your mind when focusing on your responsibility areas, it allows deeper intuition and creativity - at the sacrifice of some cross cutting creativity across teams.