kubeadm: fix crictl command for reset

[runcom]

Signed-off-by: Antonio Murdaca [email protected]

What this PR does / why we need it:

This PR is fixing kubeadm reset, we used the wrong command pipeline now that crictl has a new version out. This version targets kube master (1.9-dev) so this is the right fix.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

Fix kubeadm reset crictl command

@luxas PTAL

[luxas]

/lgtm
/approve no-issue

I'd really like if we could get the commands executed here / integration points between kubeadm and CRI documented well in https://kubernetes.io/docs/admin/kubeadm/

Please follow-up with doing that @runcom. Thanks!

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: luxas, runcom

Associated issue requirement bypassed by: luxas

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

Needs approval from an approver in each of these OWNERS Files:

• cmd/kubeadm/OWNERS [luxas]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 55682, 55444, 55456, 55717, 55131). If you want to cherry-pick this change to another branch, please follow the instructions here.