Resolving an empty storageClass closed the corner where a cross-class clone passed unchecked, and opened a worse one: the two sides of the comparison stopped being the same kind of value. The golden's class came from its bound PVC and could not move; the pool's came from today's cluster default and could. An admin moving storageclass.kubernetes.io/is-default-class, which the resolver's own comment calls the normal state midway through a swap, then failed the whole KubernetesNodes release of a pool whose disks were all on the right class, which had changed nothing, and whose storageClass is immutable so it could not answer. A pool that has already cloned now reads its class from its own bound PVC, the same authority the golden side uses. Today's default applies only to a pool with no disk yet, which is the class its first clone will actually get. Gating the guard on the already-cloned flag instead, the way the two guards above it are gated, would have spared the same pool and then let its next worker take the host-assisted copy in silence, which is the transfer this feature exists to remove. The failure message named a cluster default the render had not consulted. It is computed only when a side is empty, and interpolated unconditionally, so a mismatch between two explicit classes reported resolving to . The sentence is now built only when a side really was resolved from the default. The size floor skipped whenever the DataVolume spec omitted a size, and a golden whose spec is silent still has a bound PVC stating the allocated one. The same authority argument as the class, and it makes the gate observable: previously it could be forced either way with no test noticing, which is how it survived a mutation pass that only ever forced conditions false. Six cases, including the reviewer's own reproduction. Three of them pin precedence contracts nothing held before: the golden's declared class and size beat its PVC, and a pool's declared class beats the PVC of its own disks. The PVC is a fallback, never an override. Assisted-By: LLM Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@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.
