NAME¶

oc adm node-image monitor - Monitor new nodes being added to an OpenShift cluster

SYNOPSIS¶

oc adm node-image monitor [OPTIONS]

DESCRIPTION¶

Monitor nodes being added to a cluster using an image generated from the "oc adm node-image create" command.

After the node image ISO has been booted on the host, the monitor command reports any pre-flight validations that may have failed impeding the host from being added to the cluster. If validations are successful, the node installation starts.

Before a node joins the cluster and becomes fully functional, two certificate signing requests (CSRs) need to be approved. The monitor command will display CSRs pending your approval.

The command ends when the nodes have successfully joined the cluster.

The command creates a pod in a temporary namespace on the target cluster to monitor the nodes.

The command also requires a connection to the target cluster, and a valid registry credentials to retrieve the required information from the target cluster release.

OPTIONS¶

--certificate-authority=""
The path to a certificate authority bundle to use when communicating with the managed container image registries. If --insecure is used, this flag will be ignored.

--insecure=false
Allow push and pull operations to registries to be made over HTTP

--ip-addresses=""
IP addresses of nodes to monitor.

-a, --registry-config=""
Path to your registry credentials. Alternatively REGISTRY_AUTH_FILE env variable can be also specified. Defaults to ${XDG_RUNTIME_DIR}/containers/auth.json, /run/containers/${UID}/auth.json, ${XDG_CONFIG_HOME}/containers/auth.json, ${DOCKER_CONFIG},  /.docker/config.json,  /.dockercfg. The order can be changed via the REGISTRY_AUTH_PREFERENCE env variable (deprecated) to a "docker" value to prioritizes Docker credentials over Podman's.

--skip-verification=false
Skip verifying the integrity of the retrieved content. This is not recommended, but may be necessary when importing images from older image registries. Only bypass verification if the registry is known to be trustworthy.

OPTIONS INHERITED FROM PARENT COMMANDS¶

--as=""
Username to impersonate for the operation. User could be a regular user or a service account in a namespace.

--as-group=[]
Group to impersonate for the operation, this flag can be repeated to specify multiple groups.

--as-uid=""
UID to impersonate for the operation.

--cache-dir="/home/abuild/.kube/cache"
Default cache directory

--client-certificate=""
Path to a client certificate file for TLS

--client-key=""
Path to a client key file for TLS

--cluster=""
The name of the kubeconfig cluster to use

--context=""
The name of the kubeconfig context to use

--disable-compression=false
If true, opt-out of response compression for all requests to the server

--insecure-skip-tls-verify=false
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure

--kubeconfig=""
Path to the kubeconfig file to use for CLI requests.

--match-server-version=false
Require server version to match client version

-n, --namespace=""
If present, the namespace scope for this CLI request

--profile="none"
Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex)

--profile-output="profile.pprof"
Name of the file to write the profile to

--request-timeout="0"
The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.

-s, --server=""
The address and port of the Kubernetes API server

--tls-server-name=""
Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used

--token=""
Bearer token for authentication to the API server

--user=""
The name of the kubeconfig user to use

--warnings-as-errors=false
Treat warnings received from the server as errors and exit with a non-zero exit code

EXAMPLE¶

  # Monitor a single node being added to a cluster


  oc adm node-image monitor --ip-addresses 192.168.111.83


  


  # Monitor multiple nodes being added to a cluster by separating each


  # IP address with a comma


  oc adm node-image monitor --ip-addresses 192.168.111.83,192.168.111.84

SEE ALSO¶

oc-adm-node-image(1),

HISTORY¶

June 2016, Ported from the Kubernetes man-doc generator