clusterctl bmc redfish
clusterctl bmc redfish
clusterctl bmc redfish
Talk to the Redfish interface directly
Synopsis
Send requests to the Redfish interface of the service processors.
The certificate of each processor is pinned the first time it is seen and a change is refused, because a self signed certificate cannot be verified any other way.
clusterctl bmc redfish [flags]Options
-h, --help help for redfishOptions 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 yesSEE ALSO
- clusterctl bmc - Operate the service processors of the nodes
- clusterctl bmc redfish get - Read a Redfish resource
- clusterctl bmc redfish info - Summarise what the service processors report
- clusterctl bmc redfish post - Send an action to a Redfish resource