This document describes how to roll back the migrated resources from the global external Application Load Balancer infrastructure to the classic Application Load Balancer infrastructure.
Use the following order to roll back a migrated resource within 90 days of changing its load balancing scheme:
- Roll back the forwarding rule.
- Roll back the backend buckets.
- Roll back all the backend services attached to the forwarding rule.
To roll back a backend service to the EXTERNAL load balancing scheme, you must
first roll back the forwarding rule.
Before you begin
Before you roll back migrated resources, make sure that you've migrated the
classic Application Load Balancer resources to the global external Application Load Balancer
infrastructure and
changed their load balancing schemes to EXTERNAL_MANAGED. Remember, only
resources that were migrated to the EXTERNAL_MANAGED scheme from the
EXTERNAL scheme in the last 90 days can be rolled back.
You must also remove any advanced traffic management features configured on the resources before you start the rollback process.
Required role
To get the permissions that
you need to manage load balancer components,
ask your administrator to grant you the
Compute Network Admin (roles/compute.networkAdmin) IAM role on your project.
For more information about granting roles, see Manage access to projects, folders, and organizations.
You might also be able to get the required permissions through custom roles or other predefined roles.
For more information, see the following pages:
Roll back the forwarding rule
Console
To roll back forwarding rules, use the gcloud CLI.