Recommended usage conventions for kubectl.
kubectl in Reusable ScriptsFor a stable output in a script:
-o name, -o json, -o yaml, -o go-template, or -o jsonpath.jobs.v1.batch/myjob. This will ensure that kubectl does not use its default version that can change over time.kubectl runFor kubectl run to satisfy infrastructure as code:
:v1234, v1.2.3, r03062016-1-4, rather than :latest (For more information, see Best Practices for Configuration).kubectl run flags.You can use the --dry-run=client flag to preview the object that would be sent to your cluster, without really submitting it.
kubectl run generators are deprecated. See the Kubernetes v1.17 documentation for a list of generators and how they were used. You can generate the following resources with a kubectl command, kubectl create --dry-run=client -o yaml:
clusterrole: Create a ClusterRole.clusterrolebinding: Create a ClusterRoleBinding for a particular ClusterRole.configmap: Create a ConfigMap from a local file, directory or literal value.cronjob: Create a CronJob with the specified name.deployment: Create a Deployment with the specified name.job: Create a Job with the specified name.namespace: Create a Namespace with the specified name.poddisruptionbudget: Create a PodDisruptionBudget with the specified name.priorityclass: Create a PriorityClass with the specified name.quota: Create a Quota with the specified name.role: Create a Role with single rule.rolebinding: Create a RoleBinding for a particular Role or ClusterRole.secret: Create a Secret using specified subcommand.service: Create a Service using specified subcommand.serviceaccount: Create a ServiceAccount with the specified name.kubectl applykubectl apply to create or update resources. For more information about using kubectl apply to update resources, see Kubectl Book.
© 2022 The Kubernetes Authors
Documentation Distributed under CC BY 4.0.
https://kubernetes.io/docs/reference/kubectl/conventions/