kubesphere/kubekey

support CRI-O contianer-runtime auto installtion

Open

#1,210 opened on Apr 14, 2022

View on GitHub
 (8 comments) (0 reactions) (1 assignee)Go (820 forks)auto 404
good first issuehelp wantedkind/feature-request

Repository metrics

Stars
 (2,815 stars)
PR merge metrics
 (Avg merge 20d 9h) (31 merged PRs in 30d)

Description

Your current KubeKey version

latest

Describe this feature

support CRI-O contianer-runtime with auto installtion，but i am not sure CRI-O is good enough and how many people use in product environment:

  • containerd is Graduation status in CNCF
  • CRI-O is Hatching state in CNCF, used by openshif4.x default,

but CRI-O IS Very lightweight and Designed for k8s, i'd like to see it support by kubekey default.

Describe the solution you'd like

add CRI-O to artifact packages ,and support auto install.

Additional information

No response

Contributor guide

Research direction
Study the existing container runtime installation code (e.g., containerd) in KubeKey and replicate the pattern for CRI O, including artifact packaging and auto installation logic.
Tech stack
go
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60