This is the manual for the unreleased main branch. The latest release is v0.4.0: read its manual.
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, a sops too old to read the Secret documents.

With –remote the infrastructure hosts are contacted as well and asked whether the tools the commands rely on are installed, each role in one session, side by side, at most four sessions at once on one host, a jump host on the way counted as one too. 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 hosts

Options 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; caps the service processors and the names asked at once too, which fanout.max and CLUSTERCTL_FANOUT do not (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, jq= (default "table")
      --progress string       how to show the progress of a command on standard error: auto, tty, counter, plain, none (default: CLUSTERCTL_PROGRESS, else auto, a live tree when standard error is a terminal; plain writes lines for a log)
      --progress-log string   append the progress events of a command to this file, one JSON object per line, created readable by you alone (default: CLUSTERCTL_PROGRESS_LOG; an empty one writes none)
      --set stringArray       override one configuration value as PATH=VALUE, repeatable
  -y, --yes                   answer the confirmation prompts with yes

SEE ALSO

  • clusterctl - Administer HPC clusters from one binary