Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fargate scaling support #582

Open
villelahdenvuo opened this issue Nov 6, 2024 · 2 comments
Open

Fargate scaling support #582

villelahdenvuo opened this issue Nov 6, 2024 · 2 comments

Comments

@villelahdenvuo
Copy link

villelahdenvuo commented Nov 6, 2024

Instance scheduler now supports ECS via ASG scaling, however it does not work for Fargate services as they do not use EC2/ASGs and have their own task scaling system.

Describe the feature you'd like

Add support for Fargate task scaling to instance scheduler, similar to how ASGs work.

Additional context

The workaround is to maintain your own scaling rules for Fargate services, but the idea of having a centralized instance scheduler is nice.

Example with CDK
	/** Set up office hours scaling to save money on development environments. */
	private setupOfficeHours(scalableTarget: cdk.aws_ecs.ScalableTaskCount) {
		scalableTarget.scaleOnSchedule('OfficeHoursIn', {
			schedule: appscaling.Schedule.cron(OFFICE_HOURS.in),
			minCapacity: this.env.minCapacity ?? 1,
			maxCapacity: this.env.maxCapacity ?? 2,
		});
		scalableTarget.scaleOnSchedule('OfficeHoursOut', {
			schedule: appscaling.Schedule.cron(OFFICE_HOURS.out),
			minCapacity: 0,
			maxCapacity: 0,
		});
	}
@CrypticCabub
Copy link
Member

Thanks for creating the feature request. If anybody else would like to see Fargate scheduling support prioritized, please upvote this issue.

@bientavu
Copy link

It is indeed a really cool feature to add! This instance scheduler project is perfect, only ECS Fargate scheduling is missing (and we use it a lot)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants