Add docker ansible tag

[tu1h]

What type of PR is this?

/kind feature

What this PR does / why we need it:
Add new fine-grained tag to make it possible to skip docker installation by running the command ansible-playbook --skip-tags docker-engine ....

This is suitable for a scenario where docker is already installed on a node and there are already business applications running on top of docker, and I want to use this docker again as the underlying runtime for k8s and don't want to change any of the docker's configurations.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Add new fine-grained tag `docker-engine` to skip docker installation

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[tico88612]

@tu1h Could you rebase this PR to upstream?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tu1h
Once this PR has been reviewed and has the lgtm label, please assign oomichi for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[tu1h]

@tu1h Could you rebase this PR to upstream?

Done

[tu1h]

/ok-to-test

[tico88612]

/remove-lifecycle rotten

[tico88612]

@VannTen, what do you think of this PR?

[VannTen]

I think you can already do `deploy_container_engine: false` to not deploy docker (or anything else), is that not appropriate here for some reason ?

[tu1h]

Hi @VannTen, deploy_container_engine determines the whole things of container runtimes provisioning. For container_manager: docker, the provisioning includes the installation of docker and cri-dockerd in sequence.

In a senario, there was a already installed docker in node, but no K8s-related components (like cri-dockerd), just only intending to skip docker installation for reusing it when run ansible-playbook cluster.yml. The new tag docker-engine could make that.