kubectl run <NAME>

Create and run a particular image in a pod




--allow-missing-template-keysIf true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats
-f, --filename <File>Filename, directory, or URL to files identifying the resource
--dry-run <Strategy>Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource
-k, --kustomize <Kustomize Dir>Process the kustomization directory. This flag can't be used together with -f or -R
-R, --recursiveProcess the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory
-o, --output <Output Format>Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-file
--recordRecord current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists
--template <arg>Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview]
--annotations <arg>Annotations to apply to the pod
--attachIf true, wait for the Pod to start running, and then attach to the Pod as if 'kubectl attach ...' were called. Default false, unless '-i/--stdin' is set, in which case the default is true. With '--restart=Never' the exit code of the container process is returned
--cascade <arg>Must be "background", "orphan", or "foreground". Selects the deletion cascading strategy for the dependents (e.g. Pods created by a ReplicationController). Defaults to background
--commandIf true and extra arguments are present, use them as the 'command' field in the container, rather than the 'args' field which is the default
--env <arg>Environment variables to set in the container
--exposeIf true, service is created for the container(s) which are run
--forceIf true, immediately remove resources from API and bypass graceful deletion. Note that immediate deletion of some resources may result in inconsistency or data loss and requires confirmation
--grace-period <arg>Period of time in seconds given to the resource to terminate gracefully. Ignored if negative. Set to 1 for immediate shutdown. Can only be set to 0 when --force is true (force deletion)
--hostport <arg>The host port mapping for the container port. To demonstrate a single-machine container
--image <arg>The image for the container to run
--image-pull-policy <arg>The image pull policy for the container. If left empty, this value will not be specified by the client and defaulted by the server
-l, --labels <arg>Comma separated labels to apply to the pod(s). Will override previous values
--leave-stdin-openIf the pod is started in interactive mode or with stdin, leave stdin open after the first attach completes. By default, stdin will be closed after the first attach completes
--limits <arg>The resource requirement limits for this container. For example, 'cpu=200m,memory=512Mi'. Note that server side components may assign limits depending on the server configuration, such as limit ranges
--overrides <arg>An inline JSON override for the generated object. If this is non-empty, it is used to override the generated object. Requires that the object supply a valid apiVersion field
--pod-running-timeout <arg>The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
--port <arg>The port that this container exposes
--quietIf true, suppress prompt messages
--requests <arg>The resource requirement requests for this container. For example, 'cpu=100m,memory=256Mi'. Note that server side components may assign requests depending on the server configuration, such as limit ranges
--restart <arg>The restart policy for this Pod. Legal values [Always, OnFailure, Never]. If set to 'Always' a deployment is created, if set to 'OnFailure' a job is created, if set to 'Never', a regular pod is created. For the latter two --replicas must be 1. Default 'Always', for CronJobs `Never`
--rmIf true, delete resources created in this command for attached containers
--save-configIf true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future
--serviceaccount <arg>Service account to set in the pod spec
-i, --stdinKeep stdin open on the container(s) in the pod, even if nothing is attached
--timeout <arg>The length of time to wait before giving up on a delete, zero means determine a timeout from the size of the object
-t, --ttyAllocated a TTY for each container in the pod
--waitIf true, wait for resources to be gone before returning. This waits for finalizers