But now I can clearly see its name, I'm wondering; is the autoscaler feature only compatible with Kubernetes??? I mean, that doesn't look like the feature described in the ticket you previously shared: BCLOUD-21343
We don't use Kubernetes. So, if we want to use the autoscaler feature, that means we have to:
- develop new skills in the team.
- create a cluster (always up and running = $$$).
Do you confirm?
I was hoping to get a feature as the one that exists for Bamboo On Premise: create remote instances (AWS EC2) on demand. Why choosing a totally different approach? I only see disadvantages; more expensive, more complicated, ... :(
Atlassian Team members are employees working across the company in a wide variety of roles.
June 8, 2022 edited
Kubernetes is the first platform that we decided to support in the autoscaling tool because Linux runners are containerized, K8s is quite popular, and easy to deploy containers on it.
If we see more requests for the AWS EC2 platform we will add support for it. I am not sure about the effort required to add EC2 support. Maybe @Oleksandr Kyrdan can help us here?
That would be really useful.. As it's a feature already available On Premise, having it in the Cloud would be a smart move to encourage customers to migrate, IMHO.
113 comments