Bootstrap and control-plane providers built for the v1beta2 contract need Cluster API v1.11 or later. v1.13.7 is the newest release this cluster can move to from v1.10 in one step: upstream supports upgrades that skip at most three minor versions, so v1.14 has to follow in a later release. v1.13 still serves the v1beta1 API and accepts v1beta1-contract providers, so the providers that stay on that contract keep working; upstream stops serving v1beta1 in v1.16. The core package gains a components target in the style of the capmox and in-cluster IPAM packages: it downloads the release assets, checks them against pinned sums, applies patches/ and writes the YAML and the blob the chart mounts. The startupProbe that kept the manager alive through certificate provisioning becomes a patch instead of a hand edit of the vendored file, so a refresh carries it forward. The capmox and in-cluster IPAM pin comments named the v1.10.1 core as the reason to stay where they are. That no longer holds; the comments now give the reasons that do: the v1alpha2 API migration capmox v0.8 brings, and IPAM v1.1 moving to the v1beta2 contract while capmox v0.7 stays on v1beta1. The check that the core blob matches its YAML moves from its own bats file into the provider suite, so a failure now points at make components instead of a hand-run gzip that skips the sums and the patch. The vendored YAML carries patches/, so its sum cannot be pinned directly. The bats suite reverts the patches and checks the result against the pinned release sum instead, which catches a hand edit of the vendored file as well as a patch or a sum changed on its own. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>
Cozystack
Cozystack is a free and open-source platform and framework for building clouds.
Cozystack is a CNCF Sandbox 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 to build your own platform
You can install only the Cozystack components you need on an existing Kubernetes cluster
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 are welcome to take on the fix yourself. 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 us in #cozystack, on either CNCF Slack (get an invite) or Kubernetes Slack (get an invite), in our Telegram group, and at our community meetings. Add them to your Google Calendar or iCal for convenience.
Project documents
| Document | What it covers |
|---|---|
| Governance | How decisions are made and who makes them |
| Contributor Ladder | How to grow from contributor to maintainer |
| Maintainers | Who maintains the project |
| Code of Conduct | What we expect of each other |
| Security Policy | Reporting a vulnerability, and which releases get fixes |
| Adopters | Who runs Cozystack in production |
| Roadmap | Where the project is going |
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.
