10000 docs: add documentation for prebuild scheduling feature by evgeniy-scherbina · Pull Request #18462 · coder/coder · GitHub
[go: up one dir, main page]

Skip to content

docs: add documentation for prebuild scheduling feature #18462

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

Merged
merged 7 commits into from
Jun 20, 2025
Prev Previous commit
Next Next commit
Update docs/admin/templates/extending-templates/prebuilt-workspaces.md
Co-authored-by: Danny Kopping <danny@coder.com>
  • Loading branch information
evgeniy-scherbina and dannykopping authored Jun 20, 2025
commit 8225b60bd56097d2d79cf8e38a8f31b15b5af685
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,7 @@ data "coder_workspace_preset" "goland" {

**How scheduling works:**

1. Coder evaluates all active schedules at regular intervals.
1. The reconciliation loop evaluates all active schedules every reconciliation interval (`CODER_WORKSPACE_PREBUILDS_RECONCILIATION_INTERVAL`).
2. The schedule that matches the current time becomes active. Overlapping schedules are disallowed by validation rules.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small nit:

Suggested change
2. The schedule that matches the current time becomes active. Overlapping schedules are disallowed by validation rules.
2. The schedule matching the current time is considered active. Overlapping schedules are prevented by validation rules.

3. If no schedules match the current time, the base `instances` count is used.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small nit:

Suggested change
3. If no schedules match the current time, the base `instances` count is used.
3. If no schedule matches the current time, the system defaults to the base `instances` count.

4. The reconciliation loop automatically creates or destroys prebuilt workspaces to match the target count.
Expand Down
Loading
0