LogoLogo
WebsiteSlack
0.28
0.28
  • Get started
  • Clients
    • Install
    • CLI commands
    • Python API
    • Environments
    • Telemetry
    • Uninstall
  • Workloads
    • Realtime APIs
      • Example
      • Predictor
      • Configuration
      • Models
      • Parallelism
      • Server-side batching
      • Autoscaling
      • Statuses
      • 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
  • Update Cortex configuration
  • Upgrade to a newer version of Cortex
  • Upgrade without downtime
  1. Clusters
  2. Cortex Cloud on AWS

Update

Update Cortex configuration

cortex cluster configure  # or: cortex cluster configure --config cluster.yaml

Upgrade to a newer version of Cortex

# spin down your cluster
cortex cluster down

# update your CLI to the latest version
pip install --upgrade cortex

# confirm version
cortex version

# spin up your cluster
cortex cluster up

Upgrade without downtime

In production environments, you can upgrade your cluster without downtime if you have a backend service or DNS in front of your Cortex cluster:

  1. Spin up a new cluster. For example: cortex cluster up --config new-cluster.yaml --configure-env new (this will create a CLI environment named new for accessing the new cluster).

  2. Re-deploy your APIs in your new cluster. For example, if the name of your CLI environment for your old cluster is old, you can use cortex get --env old to list all running APIs in your old cluster, and re-deploy them in the new cluster by changing directories to each API's project folder and running cortex deploy --env new.

  3. Route requests to your new cluster.

    • If you are using a custom domain: update the A record in your Route 53 hosted zone to point to your new cluster's API load balancer.

    • If you have a backend service which makes requests to Cortex: update your backend service to make requests to the new cluster's endpoints.

    • If you have a self-managed API Gateway in front of your Cortex cluster: update the routes to use new cluster's endpoints.

  4. Spin down your old cluster. If you updated DNS settings, wait 24-48 hours before spinning down your old cluster to allow the DNS cache to be flushed.

PreviousInstallNextSecurity

Last updated 4 years ago