clusterctl doctor
clusterctl doctor
clusterctl doctor
Check that this installation can do its job
Synopsis
Check the things that go wrong quietly: a configuration that does not resolve, a missing ssh client, a host key file that is not there, an unreadable age identity.
With –remote the infrastructure hosts are contacted as well and asked whether the tools the commands rely on are installed. The checks only read, so they are made under –dry-run too.
clusterctl doctor clusterctl doctor –remote
clusterctl doctor [flags]Options
-h, --help help for doctor
--remote also contact the infrastructure hostsOptions inherited from parent commands
--config strings configuration file or directory to read, repeatable (default: CLUSTERCTL_CONFIG or the search path)
--context string context to act on (default: the current one)
--dry-run report what would be done and change nothing
--fanout int how many hosts to work on at once, at least 1 (default: from the configuration)
--force allow protected hosts, and nodes the inventory does not know, to be touched
-n, --nodes stringArray node set to act on, for example 'exe[1-10],@rack:R02' (default: CLUSTERCTL_NODES)
-o, --output string output format: table, wide, json, yaml, nodeset, name, jsonpath=, jq= (default "table")
--set stringArray override one configuration value as PATH=VALUE, repeatable
-y, --yes answer the confirmation prompts with yesSEE ALSO
- clusterctl - Administer HPC clusters from one binary