replaced deprecated 'kubectl run' for minikube setup

[sluetze]

swapped kubectl run for kubectl create -f - against stable api

fixes #10956

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: stewart-yu

If they are not already assigned, you can assign the PR to them by writing /assign @stewart-yu in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8sio-netlify-preview-bot]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit ff346cd

https://deploy-preview-11113--kubernetes-io-master-staging.netlify.com

[sluetze]

Addition: kubernetes/kubernetes#71006 seems to change the behavior of kubectl run for version v1.13 and supersedes the doc-change (at least vor v1.13)

[Bradamant3]

@sluetze it looks as though this PR should retarget the dev-1.13 branch, yes? If you could take care of it, that would be great. Thank you so much for your contribution!

[tfogo]

/assign

[tfogo]

Hi @sluetze, I'm trying to get all PRs for 1.13 merged asap. Could you let me know what the status of this PR is? Thanks!

[sluetze]

Hi @tfogo @Bradamant3,

sorry if I was not precise.
This doc change is only relevant for 1.12, since in 1.12 #10956 exists (kubectl run calls api deployment/apps.v1beta1 which is deprecated ).
Due to the change in PR kubernetes/kubernetes#71006 the issue #10956 should not exist in 1.13 (kubectl run calls api apps/v1, [I did not test this, since i don't have a 1.13 cluster deployed atm])

so there are two possibilities:

1. discard my PR, since this is only a temporary problem
2. apply my PR to 1.12 (master) and file another PR to undo this PR for dev-1.13

apply only to dev-1.13 makes no sense since it fixes nothing.
apply to 1.12 (master) and dev-1.13 makes no sense, since the deployment with kubectl create -f - is more complex than with kubectl run

[Bradamant3]

@tfogo I'll leave this one to you for final decision, but my inclination is to discard this PR since we're shipping 1.13 so soon.

[mdlinville]

I agree, please discard this PR and make a new PR targeting release-1.12 if you are still interested in fixing this for that version.