If true, use a schema to validate the input before sending it Template string or path to template file to use when -o=go-template, -o=go-template-file.

If true, keep the managedFields when printing objects in JSON or YAML format. Selector (label query) to filter on, supports '=', '=', and '!='.(e.g. This flag is useful when you want to perform kubectl apply on this object in the future. Otherwise, the annotation will be unchanged. If true, the configuration of current object will be saved in its annotation.

Useful when you want to manage related manifests organized within the same directory. Process the directory used in -f, -filename recursively. If not set, default to updating the existing annotation value only if one already exists. If set to false, do not record the command. Record current kubectl command in the resource annotation. Uses the transport specified by the kubeconfig file. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file. This flag can't be used together with -f or -R. Name of the manager used to track field ownership.įilename, directory, or URL to files to use to create the resource If server strategy, submit server-side request without persisting the resource. If client strategy, only print the object that would be sent, without sending it. Only applies to golang and jsonpath output formats.

If true, ignore any errors in templates when a field or map key is missing in the template. pod.jsonĬreate a pod based on the JSON passed into stdin cat pod.json | kubectl create -f -Įdit the data in docker-registry.yaml in JSON then create the resource using the edited data kubectl create -f docker-registry.yaml - edit -o jsonĬreate a resource from a file or from stdin. Once your workloads are running, you can use the commands in theĬreate a pod using the data in pod.json kubectl create -f.

expose will load balance traffic across the running instances, and can create a HA proxy for accessing the containers from outside the cluster.

run will start running 1 or more instances of a container image on your cluster.

This section contains the most basic commands for getting a workload

Open whitelist file