Myasnikov Daniil
ea2ad97b9e
The three format guards run for every pool, including one with osImage omitted, so they apply to values a running cluster may already hold. The schema does not stop any of them: values.schema.json and the cozyrds openAPISchema type talos.version, talos.schematicID and talos.imageFactoryURL as bare strings with no pattern, so the CR accepts a malformed one and the pool's HelmRelease is what fails. Reproduced on a live stand rather than argued from the template. A KubernetesNodes carrying talos.version "v1.13" was admitted with the value intact and its HelmRelease went InstallFailed naming the format. Editing an unrelated field on that pool afterwards -- maxReplicas 1 to 3 -- was accepted by the CR and reached .spec.values of the HelmRelease, which stayed InstallFailed: the edit is taken everywhere and applied nowhere. That is the cost being documented, and it is why the shapes are named in prose where an operator reads them. Pattern is not expressible here. cozyvalues-gen writes types.go, values.schema.json, the README table and the cozyrd from values.yaml, and its annotation set has no pattern; a pattern added to values.schema.json by hand is erased by the next make generate, which is how this was checked. Teaching the generator that annotation is the follow-up that would let the rejection land on the CR instead. schematicID already documented its shape. version and imageFactoryURL now do too, the latter noting that a builtin pool builds no source URL and so is not held to 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.