Course contentsShow
← Cloud and Infrastructure
Lesson 1898 of 2,98940. ArgoCDFree lesson

Sync Windows

Restricting application syncs to specific time windows for change management.

Sync Windows in ArgoCD

What you'll learn: How to restrict ArgoCD application syncs to approved maintenance windows for safer change management.

What Are Sync Windows?

Sync Windows let you define time-based access controls for when ArgoCD can sync applications to your cluster. Think of them as "business hours" for deployments—just like how some banks only process large transfers during specific windows, you can limit syncs to approved change windows.

This is critical for production environments with strict change management policies, regulatory requirements, or when you need to avoid deployments during peak business hours.

Why Use Sync Windows?

Without sync windows, auto-sync could deploy changes at 3 AM on Sunday or during Black Friday traffic. Sync windows give you control:

  • Change freeze periods: Block all syncs during critical business events
  • Maintenance windows: Allow syncs only during approved times (e.g., Tuesday 2-4 AM)
  • Business hours protection: Prevent risky changes during peak usage

How Sync Windows Work

Sync windows are configured at the Project level and apply to all applications within that project. You define:

  • Schedule: Days and times when syncs are allowed or denied
  • Duration: How long the window lasts
  • Action: allow or deny
  • Scope: Which applications or namespaces are affected

For example, you might create a deny window for weekdays 9 AM–5 PM and an allow window for Saturday nights 2–6 AM.

When a sync window is active and set to deny, manual syncs are blocked and auto-sync is paused. When the window closes, auto-sync resumes automatically.

Key Takeaway: Sync windows enforce time-based deployment controls in ArgoCD, ensuring changes only happen during approved maintenance windows—essential for production change management and compliance.