kubectl run command does not seems to generate deployment

Vampouille

In the "Managing State with Deployments" it says :
"The default controller for a container deployed via kubectl run command is a Deployment."
But the kubectl run command generate/deploy Pod object not Deployment :

$ kubectl run nginx --image=nginx --dry-run=client -o yaml
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  labels:
    run: nginx
  name: nginx
spec:
  containers:
  - image: nginx
    name: nginx
    resources: {}
  dnsPolicy: ClusterFirst
  restartPolicy: Always
status: {}

Napsty

Stumbled across this by chance today and will answer your question:
https://stackoverflow.com/a/65674726/7755225

Vampouille

Thanks, so kubectl run generate a Pod since 2020 (1.18)

chrispokorni

Hi @Vampouille,

The kubectl run command used to allow the creation of objects like the pod, deployment, job, etc. all with the help of a --generator flag.

Regards,
-Chris

Vampouille

@chrispokorni Since 1.18, kubectl run command generates only Pod. The offical documentation says : "Create and run a particular image in a pod."

https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#run

If you want to create Deployment, DaemonSet or Job you need to use kubectl create command.

oleksazhel

Moreover Kates 1.25 doesn't have --generator flag at all.

chrispokorni

Hi @Vampouille,

You are correct, Deployment and Job objects can be created with the kubectl create command, but not the DaemonSet object.

Also, as @oleksazhel noted, the --generator flag, which used to allow the creation of Deployment, Job, and other operators, is no longer supported.

Regards,
-Chris