Move CRI page into Containers concept section

[sftim]

This is a Feature Request

What would you like to be added
Move https://kubernetes.io/docs/concepts/architecture/cri/ to be https://kubernetes.io/docs/concepts/containers/cri/

Why is this needed
The CRI is not an important detail for people to learn about Kubernetes' overall architecture. Moving it away simplifies the learning journey for people who want to start understanding a high level overview.

Comments
/kind cleanup
/language en

If you make this change:

• label the PR as a refactor PR (or remind your reviewer to do that)
• configure a redirect - see file static/_redirects - from the old URI to the new one.

[tengqm]

I don't agree to this suggestion. The CRI is an important component in the overall architecture but it is pretty transparent to containerized applications and their developers. The current position of https://kubernetes.io/docs/concepts/containers/ is more for the latter group of people.

[sftim]

Can we move that concept page to a different target so that it's not so prominent?

My thinking: we don't introduce CNI or CSI at this point in someone's learning journey. It's OK to link to that as further reading. Putting it in the left nav makes the concept look important to someone who is new to Kubernetes; I think we could imagine a tank of “learning willpower” that our readers are using up as they explore our site.

[tengqm]

The current cluster architecture section needs some reorg. Different layers/levels of topics are mixed there with no logic.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

[Shubham82]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue 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 issues.

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle rotten