Time-sensitive environments

An environment's type defines its lifecycle: how long it runs, how it manages availability, and how resources are allocated over time. Set it under Environment Settings → Time Sensitive.

Environment types

Regular is persistent and always-on, with no schedule. It runs until you explicitly destroy it. Use it for production and any environment where downtime is not acceptable.

Time-sensitive runs on an availability schedule: Facets scales it up during active hours and scales it down (or destroys it) during off-hours. Use it for development and QA environments needed only during business hours, or any non-production infrastructure you do not want running overnight or on weekends.

Short-lived has a fixed lifespan. After the duration set in Auto Teardown After, Facets runs the configured Teardown Action (Scale Down or Destroy) automatically, with no manual intervention. Use it for feature-branch or PR environments, ephemeral CI test environments, and demo or sandbox environments.

Availability rule types

A time-sensitive environment uses one of two rules for what happens when it leaves its active window:

Scale up / scale down (recommended for cost saving) scales Deployments and StatefulSets to zero and disables CronJobs during the inactive period, while the cluster and its cloud resources stay intact. Workloads resume quickly on scale-up.

Launch / destroy destroys the cluster and all dependent infrastructure during the inactive period and re-provisions them at the start of the next active window. It saves the most cost but recovers slower (a full Terraform provision runs each cycle), and stateful data not backed up externally may be lost on each destroy.

Set an availability schedule

1. Open the environment, then Environment Settings → Time Sensitive.
2. Set Environment Type to Time Sensitive.
3. Choose the rule: Scale up / scale down or Launch / destroy.
4. Set the schedule, daily or on specific days of the week, with the active time frame.
5. Click Save Changes.