Myasnikov Daniil
6955a083c7
Self-review of the two commits above, three blockers. The golden-deletion procedure was wrong for the case it was written for. It told the operator to query live worker DataVolumes and read an empty result as permission to delete. A pool sits at zero workers whenever the autoscaler has nothing to place -- minReplicas: 0 is the default -- and it still pins its golden, so that query answers "empty" for exactly the pool whose next scale-up breaks. The pool declarations are the authority now, with the live disks as the second read; both empty is the go-ahead. Nothing asserted that the e2e suites take the clone path. Dropping the image block from the KubernetesNodes heredoc, or landing it at the wrong indent, puts the pool back on the HTTP import while every suite still passes -- the catalog imports a golden nobody clones. That is the same silent-fallback shape this branch already had to fix once, so it gets a guard, mutation-proven by deleting the block and watching it fail. The catalog suite covered only accepted input. Both `images[]` fields are `required`, and what that refusal buys is the golden's name: an entry missing either renders `talos-worker--<version>` or `talos-worker-<id>-`, and two such entries collide on one DataVolume, so the second replaces the first and every pool pinning it clones the wrong OS. Two cases now assert the refusal. 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.