Open sftim opened 1 year ago
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
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.
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.
The current cluster architecture section needs some reorg. Different layers/levels of topics are mixed there with no logic.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten /lifecycle frozen
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:
static/_redirects
- from the old URI to the new one.