Myasnikov Daniil
ceeec044ab
The second model read the same diff and reached five defects the single-model pass did not, all in code this branch added. A sibling pool answered for a pool that had never cloned. The already-cloned gate matched worker disks by the name prefix disk-system-<cluster>-<pool>-, and a pool named md0-gpu produces disks carrying md0's prefix. With the golden absent or Failed, md0's guards were suppressed by md0-gpu's disk and md0's new workers pointed at a source that was gone -- silently, which is the outcome the guards exist to prevent. Each cloned disk now names its own pool in an annotation and the match is exact. This only touches the clone path, so no existing worker's template changes. A golden that declares no StorageClass sits on whatever default was in force when CDI bound its PVC, not on today's. Substituting the current default for it could wave through a cross-class copy or refuse a pool that does match. The class now comes from the PVC, which is where the concrete value lives. More than one StorageClass may carry the default annotation at once -- the normal state midway through swapping a cluster's default -- and Kubernetes resolves it by creation time. The helper emitted every match concatenated, producing a class name that does not exist and refusing a pool whose class matched the default actually in force. It now picks the most recently created, as Kubernetes does. A Talos version was accepted without its patch segment. Both regexes took vMAJOR.MINOR, which names an artifact the Image Factory does not publish and an installer tag that does not exist, so the failure landed in the guest instead of at render. And the remedy printed by the cross-class guard could not be followed. The previous commit pointed it at the catalog entry's storageClass; the immutability guard added by this same branch rejects that edit once the golden exists, which is the only state in which this branch runs. The message now names the two moves that work: a new (schematicID, version) entry on the right class with the pool repointed at it, or deleting the golden once nothing clones it. 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.