atscalectl version
The version command displays the atscalectl version and build information. You should include this output when reporting an issue to AtScale Support.
Usage
atscalectl version
Example output
version prints a table similar to the following:
┌─────────┬───────────┬───────────── ─────────┬────────────┐
│ VERSION │ COMMIT │ DATE │ GO VERSION │
├─────────┼───────────┼──────────────────────┼────────────┤
│ 0.1.0 │ <commit> │ <date> │ go1.26.5 │
└─────────┴───────────┴──────────────────────┴────────────┘
The output table contains the following columns.
| Column | Description |
|---|---|
VERSION | The release version of the CLI. |
COMMIT | The source commit the binary was built from. |
DATE | The build timestamp in UTC. |
GO VERSION | The Go toolchain version used to build the binary. |
Output formats
version supports the standard output formats for automation and scripting:
atscalectl version -o json
atscalectl version -o yaml
For example, the following can be used by scripts to verify the installed CLI version:
atscalectl version -o json
Cluster access
version does not contact the Kubernetes cluster. It works without a kubeconfig file, access to Kubernetes, or an active cluster connection, making it useful for verifying that the CLI binary is installed correctly and available in the system PATH.
Recommendations when contacting AtScale Support
When reporting issues to AtScale Support, it is recommended you include the output of atscalectl version along with relevant command output and logs collected with atscalectl logs collect.