openshift-ex-validate-node-config man page

openshift ex validate node-config — Validate the configuration file for a node


openshift ex validate node-config [OPTIONS]


Validate the configuration file for a node.

This command validates that a configuration file intended to be used for a node is valid.

Options Inherited from Parent Commands

DEPRECATED: The API version to use when talking to the server

Username to impersonate for the operation.

Path to a cert. file for the certificate authority.

Path to a client certificate file for TLS.

Path to a client key file for TLS.

The name of the kubeconfig cluster to use

Path to the config file to use for CLI requests.

The name of the kubeconfig context to use

The Google Cloud Platform Service Account JSON Key to use for authentication.

If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.

Maximum number of seconds between log flushes

Require server version to match client version

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

The address and port of the Kubernetes API server

Bearer token for authentication to the API server.

The name of the kubeconfig user to use


// Validate node configuration file
 openshift ex validate node-config openshift.local.config/master/node-config.yaml

See Also



June 2016, Ported from the Kubernetes man-doc generator

Referenced By


Explore man page connections for openshift-ex-validate-node-config(1).

Openshift Openshift CLI User Manuals June 2016