Skip to content

Worker scanner's termination formula inflates target capacity with existing worker counts #8328

@matt-boris

Description

@matt-boris

If minCapacity is set to 1, for example, an instance will come up and say up, properly (with #8327 applied), but if minCapacity is ever updated, to say, 0, that worker should get a terminate respond from worker manager, but does not.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions