Skip to content

Allow policy to be defined that checks for and cleans up "idle" applications #11

Open
@pacphi

Description

@pacphi

Add the ability to define a policy that when executed scans for apps with one or more app instances that have been in an "idle" state (e.g., idle could mean some minimum threshold of CPU or RAM consumption or HTTP traffic) over a configurable duration (e.g., idle for 24 hours).

Large scale enterprise development is messy,... folks forget they’ve left sh*t running and this capability would offer another way for operators to get control of finite compute capacity. You might be thinking why not employ an auto scaler and policy? Thing is it’s not always consistently set up and bound to applications. And what if you truly want to scale to 0? In this case we're favoring availability of "thickly provisioned" compute.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions