Deployment Freeze is a Harness Governance feature that stops all Harness deployments. A deployment freeze helps ensure stability during periods of low engineering and support activity, such as holidays, trade shows, or company events.
Before You Begin
Deployment Freeze Overview
Typically, the more automated a deployment is, the safer it becomes. Automated deployments remove the errors that cause risk because they are a continual process. This has never been more accurate than with Harness Continuous Verification.
Yet, there are times when even the few personnel needed for Harness deployments are occupied with other events, such as holidays. In these cases, freezing deployments helps prevent deployments from introducing new issues.
Harness 24/7 Service Guard
Freezing Harness deployments does not mean that changes aren't happening in the deployment environment. User and system events are always taking place, and your microservice dependencies remain active.
Events and dependencies are why Harness 24/7 Service Guard is so powerful. 24/7 Service Guard catches problems that surface minutes or hours following deployment.
For more information, see 24/7 Service Guard.
When a Deployment Freeze is enabled, deployments cannot be started manually, and cannot be started automatically using a Trigger. The freeze applies across your Harness account. However, active deployments are allowed to complete.
Enable Deployment Freeze
The following procedure freezes both manual and Trigger-based deployments:
- In Harness Manager, select Continuous Security > Governance. The Deployment Governance page appears.
- Slide the Deployment Freeze slider to ON to enable the feature.
- In the resulting confirmation dialog, click Confirm. The Deployment Freeze is now enabled.
Add Deployment Freeze Window
By default, a Deployment Freeze takes effect account-wide as soon as you enable it, and remains in effect until you manually disable it. However, you can modify this behavior by adding Deployment Freeze Windows, which restrict the freeze to a range of days and (optionally) Harness Applications.
To add a Deployment Freeze Window:
- On the Deployment Governance page, click Add.
- In the resulting modal, you must select at least one Environment Type.
- Optionally, click Select Applications to restrict the Deployment Freeze Window to one or multiple Harness Applications.
- Use the date pickers to set a start and end date. Then click Submit.
The Deployment Governance page now displays the Deployment Freeze Window that you've set.
To add more Deployment Freeze Windows, just repeat the above procedure, starting at step 1. The Deployment Freeze Window modal will reopen in an empty state, as you saw above.
Modify Deployment Freeze Window
To edit or delete a scheduled Deployment Freeze Window, click its More Options ⋮ menu to access the options shown below.
Verify Deployment Freeze
To see the effects of Deployment Freeze, click Continuous Deployments. The Start New Deployment button is disabled.
These other Harness Manager elements are also disabled:
- Rerun deployment button in Deployments.
- Deploy button in Workflow.
- Deploy button in Pipeline.
Cancel Deployment Freeze
To disable Deployment Freeze (including any scheduled Freeze Windows), just move the Deployment Governance page's slider back to OFF, and then click Confirm when prompted.
Upgrading from a Harness Trial
If you enable Deployment Freeze while you are using Harness Community Edition, and then upgrade to Harness Essentials or Professional, your Deployment Freeze settings are retained but not applied at runtime in the Professional Edition. You must re-enable the Deployment Freeze in Harness Professional.
Review the following Harness features that help you monitor and control deployments: