Follow these steps to safely disable and remove ambient networking from your
cluster.

1. Remove all ambient policies impacting your services, ensuring no policy
   enforces strict mTLS:

   ```bash
   kubectl delete gcpservertlspolicies -n ambient-test server
   kubectl delete gcpclienttlspolicies -n ambient-test server-mtls
   kubectl delete gcpauthzpolicy -n ambient-test --all
   ```
2. Remove the label from the relevant namespace to disable traffic interception:

   ```bash
   kubectl label namespace ambient-test networking.gke.io/dataplane-mode-
   ```
3. Verify that the annotation `ambient.networking.gke.io/redirection` is removed
   from all Pods in the Namespace:

   ```bash
   kubectl get pods -n ambient-test -o yaml | grep redirection
   ```

   The output should be an empty response.
4. Optionally, if you enabled Layer 4 metrics generation, remove the metrics label
   from the namespace:

   ```bash
   kubectl label namespace ambient-test networking.gke.io/ambient-network-metrics-
   ```
5. Disable ambient networking at the cluster level to remove ambient components:

   ```bash
   gcloud container clusters update CLUSTER_NAME \
       --location=CLUSTER_LOCATION --no-enable-ambient-networking
   ```

   Replace the following:
   - `CLUSTER_NAME`: the name of the cluster.
   - `CLUSTER_LOCATION`: the Compute Engine [region or
     zone](https://docs.cloud.google.com/compute/docs/regions-zones#available) of the cluster.