Myasnikov Daniil
f489e78265
Five findings from the #3294 review rounds, each with a guard that fails without the fix. [MAJOR] The Talos<->Kubernetes support matrix keyed only on talos.version, so a pool could keep a supported talos.version and still boot a Talos release outside the kubelet's support window through image.builtin.version or image.factory.version, with no render failure. The matrix moves into a named template in _helpers.tpl and both paths consult it -- the pool default at the top of nodegroup.yaml, the resolved version where the image is resolved. A Talos minor the table does not list still passes, unchanged, because failing closed on a hand-maintained table would block an operator moving to a newer Talos before the table is updated. [MINOR] schematicID, version and imageFactoryURL reach an unquoted YAML scalar in the KubevirtMachineTemplate, and a value carrying a newline or a YAML metacharacter injects keys into the pool's own template. The schema cannot narrow them -- the pinned cozyvalues-gen derives `pattern` from the value type and has no annotation for a custom one -- so they are pattern-checked at render, which is where this chart already validates the kubelet reservation fields against the same hazard. The clone-path DataVolume name is quoted too; the HTTP url deliberately is not, because quoting it changes the KMT content hash and rolls every live worker. [MINOR] A golden was referenced only from inside a VM dataVolumeTemplates source, so nothing told an operator which pools still pinned it -- and a pool on `builtin: {}` does not name it in its own CR either. Every cloned worker disk now annotates its source golden, and the catalog documents the one read that answers "is this golden still in use". [MINOR] An images[] entry is effectively immutable once its golden exists: the DataVolume is named from (schematicID, version) while storage, storageClass and the URL are rendered into a spec that cannot be patched in place. The catalog said the opposite, inviting a `storage` bump. It now says to add a new entry instead. [MAJOR, residual] Nothing tied the parent kubernetes chart's talos defaults to kubernetes-nodes'. Both declare "keep in sync", the pool chart's `make update` copies neither, and the catalog drift guard reads only one of the two files. A one-sided bump now trips three checks instead of none. 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.