Brings two upstream fixes CDI v1.64.0 users hit in the field: - qemu-img 10.1.0-24.el9 restores HTTP imports to block volumes on 4Kn devices (DRBD/LINSTOR), the regression that kept this repo from following v1.65.0. The earlier -21 build shipped in v1.66.0 did not carry the fix, which is why this targets v1.66.1. - import-controller no longer clears event-based bound-condition annotations on every pod sync, removing the resourceVersion storm on prime PVCs during WFFC imports that starved the scheduler with FailedScheduling retries. The fix is commit e547586e9, a one-line guard in updatePvcFromPod that rides inside a squash titled after its kubevirtci changes, so neither the release notes nor the pull request title mention it. The operator manifest is refetched with make update. Two local customizations survive as patches now: the startupProbe patch gains the correct -p4 strip level (it never applied from the package directory as written), and the control-plane tolerations that were hand-edited into the manifest since v0.0.1 move into patches/tolerations.diff so the next refetch cannot drop them. Behavioral notes for this bump: CDI /metrics now requires a bearer token (nothing in this repo scrapes it); scratch PVCs inherit the target StorageClass instead of the cluster default; the PVC-rendering webhook is always registered but only matches PVCs labeled cdi.kubevirt.io/applyStorageProfile=true, which nothing here sets. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <3811295@gmail.com>
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 a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
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.
