openshift-ex-config-patch man page

openshift ex config patch — Update field(s) of a resource using a patch.

Synopsis

openshift ex config patch [Options]

Description

Patch the master-config.yaml or node-config.yaml

Options

-p, --patch=""
The patch to be applied to the resource JSON file.
--type="strategic"
The type of patch being provided; one of [json merge strategic]

Options Inherited from Parent Commands

--api-version=""
DEPRECATED: The API version to use when talking to the server

--as=""
Username to impersonate for the operation.

--certificate-authority=""
Path to a cert. file for the certificate authority.

--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

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

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

--google-json-key=""
The Google Cloud Platform Service Account JSON Key to use for authentication.

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

--log-flush-frequency=0
Maximum number of seconds between log flushes

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

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

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

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

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

Example

# Set the auditConfig.enabled value to true
%[1]s openshift.local.config/master/master-config.yaml --patch='{"auditConfig": {"enabled": true}}'

See Also

openshift-ex-config(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

openshift-ex-config(1).

Openshift CLI User Manuals Openshift June 2016