meshctl cluster deregister

Deregister a workload cluster from the Gloo management server, and clean up the associated Gloo resources from the cluster.

Synopsis

Deregistering a cluster removes the installed agent from the remote cluster as well as the other created resources such as secrets.

The name of the context of the cluster to deregister must be provided via the –remote-context flag. It is important that the remote context and the name passed as an argument are for the same cluster otherwise unexpected behavior may occur.

If the management cluster is different than the one that the current context points to then it can be provided via the –kubecontext flag.

  meshctl cluster deregister [cluster name] [flags]

Examples 

   meshctl cluster deregister --remote-context=<remote-cluster-1-context> cluster-1

Options 

    -h, --help                       help for deregister
      --release-name string        Helm release name. (default "gloo-platform")
      --remote-context string      Name of the kubeconfig context to use for the workload cluster.
      --remote-kubeconfig string   Path to the kubeconfig file for the workload cluster.
      --remote-namespace string    Namespace in the workload cluster where the Gloo agent is installed. (default "gloo-mesh")

Options inherited from parent commands 

        --kubeconfig string    Path to the kubeconfig file for the cluster.
      --kubecontext string   Kubernetes context for the cluster to run the command in.
  -n, --namespace string     Namespace to run the command in. (default "gloo-mesh")
      --plain                Disable styling for terminal output.
  -v, --verbose              Enable verbose logging.

SEE ALSO

  • meshctl cluster - Manage workload clusters that you register with the Gloo management server.