LogoLogo
WebsiteSlack
0.29
0.29
  • Get started
  • Clients
    • Install
    • CLI commands
    • Python API
    • Environments
    • Telemetry
    • Uninstall
  • Workloads
    • Realtime APIs
      • Example
      • Predictor
      • Configuration
      • Models
      • Parallelism
      • Server-side batching
      • Autoscaling
      • Statuses
      • Metrics
      • Multi-model
        • Example
        • Configuration
        • Caching
      • Traffic Splitter
        • Example
        • Configuration
      • Troubleshooting
    • Batch APIs
      • Example
      • Predictor
      • Configuration
      • Jobs
      • Statuses
    • Task APIs
      • Example
      • Definition
      • Configuration
      • Jobs
      • Statuses
    • Dependencies
      • Example
      • Python packages
      • System packages
      • Custom images
  • Clusters
    • Cortex Cloud on AWS
      • Install
      • Update
      • Security
      • Logging
      • Spot instances
      • Networking
        • Custom domain
        • HTTPS (via API Gateway)
        • VPC peering
      • Setting up kubectl
      • Uninstall
    • Cortex Cloud on GCP
      • Install
      • Logging
      • Credentials
      • Setting up kubectl
      • Uninstall
    • Cortex Core on Kubernetes
      • Install
      • Uninstall
    • Private Docker registry
Powered by GitBook
On this page
  1. Clusters
  2. Cortex Cloud on GCP

Uninstall

PreviousSetting up kubectlNextCortex Core on Kubernetes

Last updated 4 years ago

Since you may wish to have access to your data after spinning down your cluster, Cortex's bucket, stackdriver logs, and Prometheus volume are not automatically deleted when running cortex cluster-gcp down.

cortex cluster-gcp down

The cortex cluster-gcp down command doesn't wait for the cluster to spin down. You can ensure that the cluster has spun down by checking the GKE console.

Delete Volumes

The volumes used by Cortex's Prometheus and Grafana instances are not deleted by default, as they might contain important information. If these volumes are not required anymore, you can delete them in the GCP console. Navigate to the page (be sure to set the appropriate project), select the volumes, and click "Delete". The Prometheus and Grafana volumes that Cortex created have a name that starts with gke-<cluster name>-, and the kubernetes.io/created-for/pvc/name tag starts with prometheus- and grafana- respectively.

Disks