{"id":19427,"plugin_id":"plugins_6a992fa57b6481918dffd35d23f03408","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:15:34.361Z","digest":"9810c5d593121d08d0e483d3174268dddbb85c47cb7ee0ce156738158fa9eadc","against":null,"payload":{"description":"Use when the user wants to create, list, describe, delete, suspend, resume, or modify Zilliz Cloud clusters.","included_files":[],"name":"cluster","skill_md_contents":"---\nname: cluster\ndescription: Use when the user wants to create, list, describe, delete, suspend, resume, or modify Zilliz Cloud clusters.\n---\n\n## Prerequisites\n\n1. CLI installed and logged in (see setup skill).\n2. No cluster context required -- these are control-plane operations.\n\n## Commands Reference\n\n### Create a Cluster\n\n```bash\n# Serverless cluster\nzilliz cluster create \\\n  --name <cluster-name> \\\n  --type serverless \\\n  --project-id <project-id> \\\n  --region <region-id>\n\n# Free-tier cluster\nzilliz cluster create \\\n  --name <cluster-name> \\\n  --type free \\\n  --project-id <project-id> \\\n  --region <region-id>\n\n# Dedicated cluster\nzilliz cluster create \\\n  --name <cluster-name> \\\n  --type dedicated \\\n  --project-id <project-id> \\\n  --region <region-id> \\\n  --cu-type <Performance-optimized|Capacity-optimized> \\\n  --cu-size <cu-size>\n```\n\nTo find available project IDs, cloud providers, and regions:\n\n```bash\nzilliz project list\nzilliz cluster providers\nzilliz cluster regions --cloud-id <aws|gcp|azure>\n```\n\n### Create a Vector Lake instance\n\nA Vector Lake (sometimes called a \"VectorLake\" cluster) is the storage layer\nthat on-demand clusters attach to (see the `on-demand-cluster` skill). It is\ncreated via a hand-written subcommand calling\n`POST /v2/clusters/createVectorLake`:\n\n```bash\nzilliz cluster create-vectorlake \\\n  --project-id <project-id> \\\n  --region-id <region-id> \\\n  [--session-ttl <duration>] \\      # idle auto-suspend TTL, min 60s\n  [--max-query-node-cu <integer>] \\\n  [--max-query-node-replicas <integer>]\n```\n\nAfter the Vector Lake is `RUNNING`, attach a query workload with\n`zilliz on-demand-cluster create --project-id <id> --region-id <region> --cu-size <n> --cluster-name <name>`.\n\n### List Clusters\n\n```bash\nzilliz cluster list\n# Optional: --region-id <filter-by-region-id>\n# Pagination: --page-size <n> --page <n>\n# Fetch all pages: --all\n```\n\n### Describe a Cluster\n\n```bash\nzilliz cluster describe --cluster-id <cluster-id>\n```\n\n### Modify a Cluster\n\n```bash\nzilliz cluster modify --cluster-id <cluster-id-to-modify>\n# Optional: --cu-size <number-of-compute-units>, --replica <number-of-replicas>\n# Or use raw JSON: --body '{\"cuSize\": 2, \"replica\": 2}'\n```\n\n### Suspend a Cluster\n\n```bash\nzilliz cluster suspend --cluster-id <cluster-id-to-suspend>\n```\n\n### Resume a Cluster\n\n```bash\nzilliz cluster resume --cluster-id <cluster-id-to-resume>\n```\n\n### Delete a Cluster\n\n```bash\nzilliz cluster delete --cluster-id <cluster-id-to-delete>\n```\n\n### List Cloud Providers\n\n```bash\nzilliz cluster providers\n```\n\n### List Regions\n\n```bash\nzilliz cluster regions\n# Optional: --cloud-id <aws|gcp|azure>\n```\n\n## Guidance\n\n- Before creating a cluster, help the user choose a region by running `zilliz cluster providers` and `zilliz cluster regions`.\n- Cluster creation is **asynchronous**. After `cluster create`, the cluster status will be `CREATING`. Poll with `zilliz cluster describe --cluster-id <id>` until the status becomes `RUNNING` before proceeding with data-plane operations.\n- Before deleting a cluster, always confirm with the user -- this is irreversible.\n- After creating a cluster, suggest setting it as the active context with `zilliz context set --cluster-id <id>`.\n- When a cluster is suspended, remind the user it must be resumed before data-plane operations.\n- Different cluster types have different capabilities. See the \"Cluster Type Differences\" table in the setup skill for details.\n- `cluster create-vectorlake` creates a Vector Lake storage instance, not a regular cluster. Query workloads against it run on on-demand clusters (see the `on-demand-cluster` skill). Do not pass `--type` to this subcommand; it has its own dedicated parameter set.\n- `cluster list` supports a `--region-id <region>` filter for scoping to a single region.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}