cloudtaser-cli target debug

Creates a DebugReport custom resource on the target cluster and waits for the CloudTaser operator to populate it with diagnostic information.

The operator controller fills the DebugReport status with: - Beacon connectivity (address, info hash, connected status) - Port status (initialized, connected, heartbeat) - Operator info (version, secret backend, webhook readiness) - Cluster info (Kubernetes version, node count) - Operator pod status (ready, restart count, image) - Recent errors

The CR is automatically cleaned up after the report is read.

Requires the DebugReport CRD to be installed (included in operator >= 0.16.0) and a running CloudTaser operator in the target namespace.

Usage

cloudtaser-cli target debug [flags]

Examples

# Collect a debug report
  cloudtaser-cli target debug

  # JSON output for automation or support tickets
  cloudtaser-cli target debug --json

  # Custom namespace and timeout
  cloudtaser-cli target debug -n my-namespace --timeout 120s

  # Use a specific kubeconfig
  cloudtaser-cli target debug --kubeconfig ~/.kube/staging

Flags

Flag	Type	Default	Required	Description
--help, -h	bool	false	no	help for debug
--json	bool	false	no	output as JSON
--kubeconfig	string	(empty)	no	path to kubeconfig file
--namespace, -n	string	cloudtaser-system	no	namespace where the operator is running
--timeout	duration	1m0s	no	timeout waiting for operator to populate the report

All commands