7ab6283c14
## What this PR does Adds infrastructure support for restricting tenant workloads to specific data centers (or node groups) via SchedulingClass CRs. - Adds `schedulingClass` parameter to the Tenant model, inherited by child tenants (children cannot override parent's scheduling constraints) - Adds `scheduling.cozystack.io/class` label to tenant namespaces - Adds SchedulingClass dropdown to the Tenant creation form in the dashboard - Extends lineage-controller-webhook to inject `schedulerName: cozystack-scheduler` and `scheduler.cozystack.io/scheduling-class` annotation into all Pods in namespaces with the scheduling label - Webhook verifies the referenced SchedulingClass CR exists before injection; if missing (scheduler not installed), pods are left untouched ### Operators without native schedulerName support The following operators do not support `schedulerName` in their CRDs, but are still covered by the webhook-based approach since it mutates pods directly: - etcd-operator - redis-operator (spotahome) - mariadb-operator - clickhouse-operator (altinity) ### Release note ```release-note [scheduler] Add SchedulingClass support for tenant workloads. Administrators can assign a SchedulingClass to a tenant, restricting where its workloads are scheduled. The lineage-controller-webhook injects the custom scheduler into all pods in the tenant namespace. ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added a schedulingClass parameter for tenant configuration; it can be set in values, appears in schema/docs, inherits to namespaces, and is included in exported tenant manifests. * When present, the schedulingClass is propagated to namespace metadata and applied to workloads so scheduler selection and scheduling annotations reflect the setting. * **Bug Fixes** * Improved owner-resolution and labeling so resources and scheduling are associated more accurately. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .github | ||
| api | ||
| cmd | ||
| dashboards | ||
| docs | ||
| examples | ||
| hack | ||
| img | ||
| internal | ||
| packages | ||
| pkg | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| ADOPTERS.md | ||
| AGENTS.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CONTRIBUTOR_LADDER.md | ||
| go.mod | ||
| go.sum | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| Makefile | ||
| README.md | ||
Cozystack
Cozystack is a free PaaS platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have Feature Requests please use the Discussion's Feature Request section.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.