Skip to content

clusters rename

upgradescope clusters rename

Rename a cluster; its history and ingest tokens move with it

Synopsis

Rename a cluster; its history and its per-cluster ingest tokens move to the new name. The agent sends its own --cluster-name with every push, so change that too (chart value agent.clusterName). Until then its pushes are refused when it uses a per-cluster token (now bound to the new name), or register the old name again when it uses the shared one. The new name must be an RFC 1123 subdomain (lowercase alphanumerics, '-' and '.', at most 253 bytes), as pushes require: renaming is how a cluster a v0.1 server registered under another name (Prod_EU) moves to one its agent can push under.

upgradescope clusters rename <cluster> <new-name> [flags]

Examples

  upgradescope clusters rename prod-eu prod-eu-1 --server-url https://upgradescope.example.com

Options

      --admin-token string        with --server-url: the server's admin token (serve --admin-token) (visible in process listings: prefer $UPGRADESCOPE_ADMIN_TOKEN or --admin-token-file)
      --admin-token-file string   read --admin-token from this file, e.g. a mounted Secret (surrounding whitespace is trimmed)
      --db string                 path to the SQLite database (parent directory is created) (default "upgradescope.db")
      --db-url string             Postgres URL (postgres://user:pass@host:5432/db); mutually exclusive with --db (visible in process listings: prefer $UPGRADESCOPE_DB_URL or --db-url-file)
      --db-url-file string        read --db-url from this file, e.g. a mounted Secret (surrounding whitespace is trimmed)
  -h, --help                      help for rename
      --server-ca-file string     PEM bundle of a private CA that issued the server's certificate, trusted on top of the system roots (for an https server behind a private CA; on Linux and other Unix systems $SSL_CERT_FILE and $SSL_CERT_DIR also change the system roots, for the whole process; Go ignores them on macOS and Windows, where this flag is the way); needs an https server URL. Verification is never skipped
      --server-url string         base URL of a running upgradescope server, e.g. https://upgradescope.example.com (instead of --db/--db-url)

SEE ALSO