Enable permissive mode on a backup plan

Autopilot Standard

---

This page explains how to enable permissive mode on a backup plan.

During backup execution, if Backup for GKE detects conditions that are likely to cause restore to fail, the backup itself fails. The reason for the failure is provided in the backup's state_reason field. In the Google Cloud console, this field is termed as Status reason.

If you enable permissive mode, the description of the issue is still provided in the Status reason field, but the backup won't fail. You can enable this behavior if you are aware of the issue and are prepared to employ a workaround at restore time.

The following is an example of an error message that you might see in the backup's Status reason field that suggests enabling permissive mode: If you cannot implement the recommended fix, you may create a new backup with Permissive Mode enabled.

gcloud

Enable permissive mode:

gcloud beta container backup-restore backup-plans update BACKUP_PLAN \
    --project=PROJECT_ID \
    --location=LOCATION
    --permissive-mode

Replace the following:

• BACKUP_PLAN: the name of the backup plan that you want to update.
• PROJECT_ID: the ID of your Google Cloud project.

• LOCATION: the compute region for the resource, for example us-central1. See About resource locations.

  For a full list of options, refer to the gcloud beta container backup-restore backup-plans update documentation.

Console

Use the following instructions to enable permissive mode in the Google Cloud console:

1. In the Google Cloud console, go to the Google Kubernetes Engine page.

   Go to Google Kubernetes Engine

2. In the navigation menu, click Backup for GKE.

3. Click the Backup plans tab.

4. Expand the cluster and click the plan name.

5. Click the Details tab to edit the plan details.

6. Click Edit to edit the section with Backup mode.

7. Click the Permissive mode checkbox and click Save changes.