Aleksei Sviridkin
7badbacc3a
Re-vendors the HAMi vGPU chart from 2.8.1 to 2.9.0, moving the device-plugin image to projecthami/hami:v2.9.0 and picking up the published security fixes. The vendoring approach changed for 2.9.0: upstream now gates the scheduler and device-plugin templates on .Values.dra.enabled and .Values.podSecurityPolicy.enabled across ~27 files, so the previous "strip the dra/PSP values and remove the conditionals" approach would nil-pointer at render time. Instead the dra and podSecurityPolicy blocks are KEPT at their upstream default (enabled: false), which cleanly disables both paths; only the unused hami-dra subchart and its values block are removed. Replays the indent->nindent patch on the custom Service labels block, now extended to BOTH Services that carry the upstream defect: the device-plugin monitor Service and the scheduler Service (the latter was previously unpatched and would emit invalid YAML if scheduler.service.labels were set). Adds helm-unittest coverage (the package shipped none): pins the device-plugin image and guards the nindent patch on both Services. Adaptations: - Makefile: pin update to --version 2.9.0; keep dra/podSecurityPolicy blocks (drop the del); add test target; refresh vendoring notes - charts/: re-vendored HAMi 2.9.0 (hami-dra subchart removed, deps emptied) - charts/.../device-plugin/monitorservice.yaml + scheduler/service.yaml: replay indent->nindent - values.yaml: refresh the upstream-values reference URL to v2.9.0 - tests/hami_test.yaml: new helm-unittest coverage Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
Cozystack
Cozystack is a free 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.