Container Runtime docs: "Kata Containers as a RuntimeClass" option is not actually demonstrated or currently supported
- Dominant language
- MDX
- Stars
- 64
- Forks
- 203
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 8
Description
The Container Runtime setup page (Kata Containers section) lists two options for configuring containerd with Kata: "Kata Containers as a RuntimeClass" and "Kata Containers as a runtime for untrusted workloads." Only the untrusted-workload option is actually shown with an example (the annotation-based nginx-untrusted.yaml). There's no spec.runtimeClassName example, and the page doesn't mention that RuntimeClass support on KubeEdge edge nodes is still incomplete.
This is confirmed by kubeedge/kubeedge#7106, #6334, and #4416 - as recently as 2025 a maintainer confirmed RuntimeClass still isn't supported on edge nodes. The doc was last updated Dec 2023, so it predates that confirmation.
Listing "as a RuntimeClass" as an available option without any caveat could mislead users into thinking it works today. Suggest either adding a note clarifying current limitations with a link to kubeedge/kubeedge#7106, or removing that bullet until it's actually supported.
Contributor guide
Research direction
Start at the Container Runtime setup page's Kata Containers section and compare the RuntimeClass bullet with the demonstrated untrusted-workload option and nginx-untrusted.yaml. Review kubeedge/kubeedge#7106, #6334, and #4416 for the current support status. Done means the page either documents the limitation with a link to #7106 or removes the unsupported option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100