This is the manual for the unreleased main branch. The latest release is v0.4.0: read its manual.
Command reference
clusterctl dhcp

clusterctl dhcp

clusterctl dhcp

Read what the DHCP server knows about the nodes

Synopsis

Read the DHCP server’s configuration and log: the addresses, hardware addresses, client identifiers and boot files it hands to the nodes.

The configuration is parsed rather than grepped, so a declaration whose options are in an unusual order reports its own values and not a neighbour’s. Files named by include statements are read too, and a construct the parser does not understand is an error. A command reads the configuration once, however many nodes it asks about, and a server that could not be read is not asked again for the next node. A fetched copy is reused by the commands that follow for services.dhcp.cacheTtl, two minutes unless it says otherwise.

clusterctl dhcp [flags]

Options 

  -h, --help   help for dhcp

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 copyclusterctl dhcp capture