Add a mapping table from docker cli to crictl in crictl debugging doc

[qiutongs]

Signed-off-by: Qiutong Song [email protected]

Add a mapping table from docker cli to crictl in crictl debugging doc. This table serves as a convenient reference when users want to use crictl. This is important especially if users are going to use ContainerD as the container runtime.

[netlify]

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

Built with commit aa88030

https://deploy-preview-25109--kubernetes-io-master-staging.netlify.app

[sftim]

I like the idea of these tables @qiutongs

However, I have some thoughts / questions:

1. could these tables actually live inside https://github.com/kubernetes-sigs/cri-tools/tree/master/docs instead?
2. alternatively, could these tables live inside https://kubernetes.io/docs/reference/
3. if keeping the doc on this site, please add captions to each table for improved accessibility.
4. I would use code style for items such as --disable-content-trust

[derekwaynecarr]

this looks great, and is a nice location for the material.

[derekwaynecarr]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 4f083c663ecbb7144844e3713489b9ff4170b439

[SergeyKanzhelev]

/lgtm
@qiutongs can you please link to this cheat sheet from the deprecation FAQ here: https://kubernetes.io/blog/2020/12/02/dockershim-faq/#what-should-i-look-out-for-when-changing-cri-implementations:~:text=For%20the%20former%2C%20you%20can%20use%20the%20crictl%20tool%20as%20a%20drop%2Din%20replacement and address the styling and accessibility comments from @sftim

[qiutongs]

I like the idea of these tables @qiutongs

However, I have some thoughts / questions:

1. could these tables actually live inside https://github.com/kubernetes-sigs/cri-tools/tree/master/docs instead?
2. alternatively, could these tables live inside https://kubernetes.io/docs/reference/
3. if keeping the doc on this site, please add captions to each table for improved accessibility.
4. I would use code style for items such as --disable-content-trust

@sftim Hi Tim, thank you for the feedback.

• For your suggested places, they also make sense to me. But I also asked Derek and Davanum in the slack channel and they think the current place is fine. So I would just leave it.
• I will update the doc for Search Results page is quite ugly #3 and Import favicon stuff from existing site #4.

[qiutongs]

/lgtm
@qiutongs can you please link to this cheat sheet from the deprecation FAQ here: https://kubernetes.io/blog/2020/12/02/dockershim-faq/#what-should-i-look-out-for-when-changing-cri-implementations:~:text=For%20the%20former%2C%20you%20can%20use%20the%20crictl%20tool%20as%20a%20drop%2Din%20replacement and address the styling and accessibility comments from @sftim

@SergeyKanzhelev Yes, I will add it.

[sftim]

/approve

[sftim]

Aside: the first two columns could go in backticks

[qiutongs]

Sure. Let me update.

[sftim]

Oh actually, is inspectinspecti a bug?

[qiutongs]

Oops, missed a separator. Let me fix

[sftim]

/lgtm
/sig node
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 0e5357f875c8795f2d4bdfd314b8cdd92e2fd700

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sftim

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 [sftim]

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

[sftim]

Future code change spelunkers: this kind of table does usually have a better home in the reference section; however, in the interests of expediency I'm happy to see the PR merge as-is.