Synopsis
This command helps to diagnose, validate and debug the cluster and its environment. See subcommands for various functionalities.
Usage:
gkectl diagnose [command]
Available Commands:
cluster Diagnose a cluster.
snapshot Take a snapshot of the cluster.
Flags:
--cluster string The name of the kubeconfig cluster to use
--cluster-name string The name of the cluster that is managed by the Admin Control Plane.
-h, --help help for diagnose
--kubeconfig string The file path of the kubeconfig file for the Admin Control Plane. If not specified, $KUBECONFIG environment variable or ${HOME}/.kube/config is used. --cluster-name can be used to specify the target user cluster.
-n, --namespace string If present, the namespace scope for this CLI request
--user string The name of the kubeconfig user to use
Global Flags:
--alsologtostderr log to standard error as well as files
--log_file string If non-empty, use this log file
--skip_headers If true, avoid header prefixes in the log messages
--stderrthreshold severity logs at or above this threshold go to stderr (default 2)
-v, --v Level log level for V logs (default 0)
Use "gkectl diagnose [command] --help" for more information about a command.
gkectl diagnose cluster
This command performs health checks on the cluster and reports errors if there are any.
Usage:
gkectl diagnose cluster [flags]
Flags:
-h, --help help for cluster
Global Flags:
--alsologtostderr log to standard error as well as files
--cluster string The name of the kubeconfig cluster to use
--cluster-name string The name of the cluster that is managed by the Admin Control Plane.
--kubeconfig string The file path of the kubeconfig file for the Admin Control Plane. If not specified, $KUBECONFIG environment variable or ${HOME}/.kube/config is used. --cluster-name can be used to specify the target user cluster.
--log_file string If non-empty, use this log file
-n, --namespace string If present, the namespace scope for this CLI request
--skip_headers If true, avoid header prefixes in the log messages
--stderrthreshold severity logs at or above this threshold go to stderr (default 2)
--user string The name of the kubeconfig user to use
-v, --v Level log level for V logs (default 0)
gkectl diagnose snapshot
This command takes a snapshot of the cluster's logs, configurations and other data.
Usage:
gkectl diagnose snapshot [flags]
Flags:
--admin-ssh-key-path string Override the private key to use when creating a snapshot. Found, base64 encoded, in create-config.yaml at admincluster.spec.ssh.privatekey.
--config string The config file of the snapshot. When this flag is omitted, a default configuration is applied.
--dry-run In dry-run mode, the command does not take the snapshot. Instead, it prints out the actions to be taken and the snapshot configuration.
-h, --help help for snapshot
--output string The output file of the snapshot.
--scenario string The scenario of the snapshot. This is ignored when --config flag is specified. The supported scenarios are:
- system: snapshot of system components, no logs, current default
- system-with-logs: snapshot of system components, including logs
- all: snapshot of all components, no logs
- all-with-logs: snapshot of all components, including logs (default "system")
Global Flags:
--alsologtostderr log to standard error as well as files
--cluster string The name of the kubeconfig cluster to use
--cluster-name string The name of the cluster that is managed by the Admin Control Plane.
--kubeconfig string The file path of the kubeconfig file for the Admin Control Plane. If not specified, $KUBECONFIG environment variable or ${HOME}/.kube/config is used. --cluster-name can be used to specify the target user cluster.
--log_file string If non-empty, use this log file
-n, --namespace string If present, the namespace scope for this CLI request
--skip_headers If true, avoid header prefixes in the log messages
--stderrthreshold severity logs at or above this threshold go to stderr (default 2)
--user string The name of the kubeconfig user to use
-v, --v Level log level for V logs (default 0)
