I\'m using kubectl run with environment parameters to create temporary docker containers for me (e.g. some forwarding for debugging purposes).
Since several wee
kubectl run by default, will create a Deployment.
The command in its full extend is:
kubectl run --generator=deployment/apps.v1 --image=
So the kubernetes resource that will be created upon execution of the run command is defined by the value of the --generator flag.
What the deprecation message hints (and is also clarified by the answer provided by @soltysh) is that the particular practice will be removed.
So in future kubernetes versions, the run command will by default (and as only option) create pods (and not deployments), i.e. the command in its full extend will become:
kubectl run --generator=run-pod/v1 --image=
In case you want to create any other kubernetes resource type, this will be impossible via run command so you will have to resort to explicit imperative create or declarative apply -f, the later pointing to kubernetes yml files with the corresponding resource defintition, as in
kubernetes apply -f