IvanHunters
5cd2502d01
The Phase 2 split makes the parent chart render control-plane-only and relies on the platform migration (a pre-upgrade hook) having adopted each worker pool onto its child kubernetes-nodes release first. If that migration does not run (its version slot was already stamped, or it was renumbered out on a merge/backport), the live worker MachineDeployment is still owned by this release and Helm's control-plane-only re-render would prune it, cascade-deleting the tenant's worker VMs. Add a render-time guard: on an upgrade, when the render can see the cluster (release-namespace canary lookup non-nil, so client-side renders stay a no-op), look up worker MachineDeployments whose spec.clusterName is this cluster and whose meta.helm.sh/release-name is still this parent release (un-adopted) and fail with a legible message instead of rendering. The upgrade blocks with a reason and the workers keep running on the prior release until the migration runs. Discriminates on the adoption annotation, not mere existence, so it does not deadlock the routine upgrade (the MD always exists at render time); mirrors the fail-closed canary pattern of system/seaweedfs naming-guard. Inert offline; the live-fail path is covered by the upgrade-adoption e2e. Signed-off-by: IvanHunters <xorokhotnikov@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.