glooctl cluster deregister

glooctl cluster deregister

Deregister a cluster to the Gloo Federation control plane

Synopsis

Deregister a cluster from the Gloo Federation control plane. Deregistered clusters can no longer be targeted for discovery and configuration. This will not delete the cluster or the managing namespace, but it will delete the service account, cluster role, and cluster role binding created on the remote cluster during the cluster registration process.

glooctl cluster deregister [flags]

Options

      --cluster-name string           name of the cluster to deregister
      --federation-namespace string   namespace of the Gloo Federation control plane (default "gloo-fed")
  -h, --help                          help for deregister
      --remote-context string         name of the kubeconfig context to use for deregistration
      --remote-kubeconfig string      path to the kubeconfig from which the deregistered cluster will be accessed
      --remote-namespace string       namespace in the target cluster where artifacts should be deleted (default "gloo-fed")

Options inherited from parent commands

  -c, --config string              set the path to the glooctl config file (default "<home_directory>/.gloo/glooctl-config.yaml")
      --consul-address string      address of the Consul server. Use with --use-consul (default "127.0.0.1:8500")
      --consul-datacenter string   Datacenter to use. If not provided, the default agent datacenter is used. Use with --use-consul
      --consul-root-key string     key prefix for for Consul key-value storage. (default "gloo")
      --consul-scheme string       URI scheme for the Consul server. Use with --use-consul (default "http")
      --consul-token string        Token is used to provide a per-request ACL token which overrides the agent's default token. Use with --use-consul
  -i, --interactive                use interactive mode
      --kubeconfig string          kubeconfig to use, if not standard one
      --use-consul                 use Consul Key-Value storage as the backend for reading and writing config (VirtualServices, Upstreams, and Proxies)

SEE ALSO