Maintenance Windows
Schedule and manage maintenance windows for your installations
Enterprise customers often request the ability to control when updates can occur in their environments. Maintenance windows satisfy this requirement by letting them define specific time periods when automated updates are allowed, helping them feel more comfortable with continuous deployment practices.
Understanding Maintenance Windows
Maintenance windows address common enterprise customer concerns about continuous deployment:
- Control over when changes can occur in their environment
- Predictability around update schedules
- Protection of peak business hours
- Alignment with their existing change management processes
Configuring Maintenance Windows
To configure maintenance windows for your environment:
Navigate to Environments
Go to the Environments tab in the Ryvn Dashboard
Select Environment
Choose the environment you want to configure
Access Maintenance Windows
Click on the Maintenance Windows section
Add New Window
Click Add Maintenance Window
Configure Window
- Set the start time (e.g.,
22:00) - Set the end time (e.g.,
04:00) - Select the timezone from the dropdown menu
- Select the checkboxes for each day you want the maintenance window to be active
Save
Click Save to apply your configuration
All times are specified in 24-hour format and must include a timezone. Updates will only start during these windows.
How Maintenance Windows Work
When a maintenance window is configured:
Schedule Definition
Your customer specifies their preferred update times based on their operational requirements.
Update Queueing
Updates that arrive outside the maintenance window are queued until the next available window.
Execution
Automated rollbacks with health check monitoring are available as an enterprise feature. Contact us to learn more.
Types of Updates
The following updates respect maintenance windows:
| Update Type | Description |
|---|---|
| Platform Updates | Operating system and runtime updates |
| Security Patches | Critical security fixes |
| Infrastructure Changes | Underlying infrastructure modifications |
| Automated Deployments | If configured, automated deployments from your repository |
Critical security updates may be applied outside maintenance windows if necessary to protect your environments. Customers are always notified when this occurs.
Best Practices
Monitoring Updates
Customers can track update activities in the Activity tab of their environment:
- Scheduled updates waiting for the next window
- Updates in progress during active windows
- Completed update history
Updates that start during a maintenance window will complete even if they extend beyond the window’s end time.