SovereignCloudStack / SovereignCloudStack/cluster-stacks
Evaluate the use of a general purpose Image
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
As capi images will not be mandatory on SCS-clouds, capo can not rely on the existence of them. Instead, one flavor on SCS is actually mandatory (Ubuntu 22.04). That means, that every capo can rely on the existence of this image. The task of this issue is to evaluate how much of an effort it is to use such a general purpose image and use it as the base-images for cluster-api workload-cluster nodes.
Contributor guide
No contributing guide indexed for this repository
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 tracing how CAPO workload-cluster nodes currently select base images and where the dependency on optional CAPI images is defined. Compare that flow with the mandatory Ubuntu 22.04 image in the SCS standard; the evaluation is complete when the implementation effort, affected configuration, and required changes are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, ubuntu
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100