Closed daniel-cit closed 1 year ago
At least these step cloud be executed before destroying the infrastructure:
export GKE_PROJECT_ID=<YOUR-GKE-PROJECT-ID>
gcloud container hub memberships unregister gke-1-boa-d-us-east1 \
--project=$GKE_PROJECT_ID \
--gke-cluster=us-east1/gke-1-boa-d-us-east1
gcloud container hub memberships unregister gke-2-boa-d-us-west1 \
--project=$GKE_PROJECT_ID \
--gke-cluster=us-west1/gke-2-boa-d-us-west1
gcloud container hub memberships unregister mci-boa-d-us-east1 \
--project=$GKE_PROJECT_ID \
--gke-cluster=us-east1/mci-boa-d-us-east1
gcloud services disable anthos.googleapis.com --force --project=$GKE_PROJECT_ID
gcloud alpha container hub ingress disable --force --project=$GKE_PROJECT_ID
$ curl -H "Authorization: Bearer $(gcloud auth print-access-token)" \
-X "DELETE" \
https://gkehub.googleapis.com/v1alpha1/projects/$GKE_PROJECT_ID/locations/global/features/authorizer
$ curl -H "Authorization: Bearer $(gcloud auth print-access-token)" \
-X "DELETE" \
https://gkehub.googleapis.com/v1alpha1/projects/$GKE_PROJECT_ID/locations/global/features/metering
gcloud services disable gkehub.googleapis.com --force --project=$GKE_PROJECT_ID
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days
Expected Behavior
There is instructions to undo configurations, like registering a cluster on Anthos in step 6, that are manual
Actual Behavior
There is no instructions to undo configurations that are manual.
Steps to Reproduce the Problem
Specifications