Add custom CRI-O configuration for k8s installation
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
To integrate sysbox with other tooling it would be nice to be able to have a custom CRI-O config.
I'd like, for example, to integrate sysbox with the Stargz Snapshotter in an automated way.
This issue aims to discuss whether it's possible to include extra config files during sysbox installation to the CRI-O service and track work on documenting that.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the sysbox installation path and existing CRI-O service configuration, then compare the Stargz Snapshotter installation requirements linked in the issue. Define how extra config files would be supplied during installation and document the supported setup, including how to verify the CRI-O integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100