SovereignCloudStack / SovereignCloudStack/cluster-stacks
Policies for each clusterclass
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
As a SCS-user it would be great to get an error message or a warning if i try to deploy an invalid, cluster spec (kube_vip with k8s > 1.28 for example). I propose to write the policies in kubernetes resources, so that they can be deployed together with the clusterclass.
Possible solutions to have a look into: kyverno, OPA.
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 from the ClusterClass deployment flow and the invalid kube_vip with Kubernetes greater than 1.28 example. Compare Kyverno and OPA for expressing policies as Kubernetes resources that deploy with the ClusterClass. Done means invalid cluster specifications produce an error or warning and the selected policies are deployed with the ClusterClass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100