Edit This Page

kubectl Usage Conventions

Recommended usage conventions for kubectl.

Using kubectl in Reusable Scripts

For a stable output in a script:

Best Practices

kubectl run

For kubectl run to satisfy infrastructure as code:


You can create the following resources using kubectl run with the --generator flag:

Resourcekubectl command
Podkubectl run --generator=run-pod/v1
Replication controllerkubectl run --generator=run/v1
Deploymentkubectl run --generator=extensions/v1beta1
-for an endpoint (default)kubectl run --generator=deployment/v1beta1
Deploymentkubectl run --generator=apps/v1beta1
-for an endpoint (recommended)kubectl run --generator=deployment/apps.v1beta1
Jobkubectl run --generator=job/v1
CronJobkubectl run --generator=batch/v1beta1
-for an endpoint (default)kubectl run --generator=cronjob/v1beta1
CronJobkubectl run --generator=batch/v2alpha1
-for an endpoint (deprecated)kubectl run --generator=cronjob/v2alpha1

If you do not specify a generator flag, other flags prompt you to use a specific generator. The following table lists the flags that force you to use specific generators, depending on the version of the cluster:

Generated ResourceCluster v1.4 and laterCluster v1.3Cluster v1.2Cluster v1.1 and earlier
Pod--restart=Never--restart=Never--generator=run-pod/v1--restart=OnFailure OR --restart=Never
Replication Controller--generator=run/v1--generator=run/v1--generator=run/v1--restart=Always
Job--restart=OnFailure--restart=OnFailure--restart=OnFailure OR --restart=NeverN/A
Cron Job--schedule=<cron>N/AN/AN/A
Note: These flags use a default generator only when you have not specified any flag. This means that when you combine --generator with other flags the generator that you specified later does not change. For example, in a cluster v1.4, if you initially specify --restart=Always, a Deployment is created; if you later specify --restart=Always and --generator=run/v1, a Replication Controller is created. This enables you to pin to a specific behavior with the generator, even when the default generator is changed later.

The flags set the generator in the following order: first the --schedule flag, then the --restart policy flag, and finally the --generator flag.

To check the final resource that was created, use the --dry-run flag, which provides the object to be submitted to the cluster.

kubectl apply