cloudtaser-cli debug¶
Collects diagnostics from all reachable CloudTaser contexts (Kubernetes, vault, beacon) and produces a unified report with cross-context coherence checks and anomaly detection.
The output is safe to share with support@cloudtaser.io -- fingerprints are truncated and no secret values are included in text output.
Examples: # Basic check against current kubeconfig context cloudtaser-cli debug
# Full check with secret store and beacon cloudtaser-cli debug --secretstore-address https://vault.example.com:8200 \ --secretstore-token-file /path/to/token --beacon-address beacon.example.com:443
# JSON output for automation cloudtaser-cli debug --json
# Save report to file cloudtaser-cli debug --output report.txt
Usage¶
Flags¶
| Flag | Type | Default | Required | Description |
|---|---|---|---|---|
--beacon-address |
string | (empty) |
no | beacon relay address (auto-detected from operator if available) |
--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 | CloudTaser namespace |
--output |
string | (empty) |
no | write report to file (default: stdout) |
--secretstore-address |
string | (empty) |
no | secret store (OpenBao/Vault) address (e.g. https://vault.example.com:8200) |
--secretstore-token |
string | (empty) |
no | secretstore token for detailed checks |
--secretstore-token-file |
string | (empty) |
no | path to file containing secretstore token, or '-' for stdin |
--timeout |
duration | 20m0s |
no | maximum time for the command to complete (default 20m0s; also CLOUDTASER_TIMEOUT env) |