Vultr DocsLatest Content

How to Update a Vultr Kubernetes Engine Cluster

Updated on 10 September, 2025

Learn how to update your Vultr Kubernetes Engine (VKE) clusters label to better organize and identify your clusters without disrupting workloads or configurations.

Updating a Vultr Kubernetes Engine (VKE) cluster enables you to change its label without affecting workloads, configurations, or underlying resources. Labels help you effectively manage multiple clusters, ensuring clear identification and organization within your infrastructure.

Follow this guide to update a Vultr Kubernetes Engine cluster in your Vultr account using the Vultr Customer Portal, API, CLI, or Terraform.

  • Vultr Customer Portal
  • Vultr API
  • Vultr CLI
  • Terraform
  1. Navigate to Products and click Kubernetes.
  2. Click your target VKE cluster to open its management page.
  3. In the Overview section, find the cluster's Label.
  4. Click the edit icon and update the Label with the appropriate name.

  1. Send a GET request to the List all Kubernetes Clusters endpoint and note the target VKE cluster's ID.

    console 
    $ curl "https://api.vultr.com/v2/kubernetes/clusters" \
    -X GET \
    -H "Authorization: Bearer ${VULTR_API_KEY}"

  2. Send a PUT request to the Update Kubernetes Cluster endpoint to update the label of the target VKE cluster.

    console 
    $ curl "https://api.vultr.com/v2/kubernetes/clusters/{cluster-id}" \
    -X PUT \
    -H "Authorization: Bearer ${VULTR_API_KEY}" \
    -H "Content-Type: application/json" \
    --data '{
        "label": "{updated-cluster-name}"
    }'

  1. List the available VKE clusters and note the target VKE cluster's ID.

    console 
    $ vultr-cli kubernetes list --summarize

  2. Update the target VKE cluster.

    console 
    $ vultr-cli kubernetes update <cluster-id> --label "<updated-cluster-name>"

  1. Open your Terraform configuration for the existing VKE cluster.

  2. Change the label and apply.

    terraform 
    resource "vultr_kubernetes" "vke" {
    # ...existing fields (region, version, node_pools)
    label = "updated-cluster-name"
}

  3. Apply the configuration and observe the following output:

    Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Comments

No comments yet.