IvanHunters 31fac3c4f1 fix(kubernetes): guard on child-release ownership, not parent release-name
The worker-adoption render guard required meta.helm.sh/release-name == the
parent release as a precondition to refuse a control-plane-only render. But
Helm's prune gates solely on helm.sh/resource-policy=keep and never consults
the live release-name (migration 54 documents this and its foreign-owner branch
depends on it). A same-cluster, unpinned worker MachineDeployment whose
release-name is empty (Helm annotations stripped out-of-band, or a DR restore
of the CAPI objects) or foreign therefore slipped past the guard, yet Helm
still entered it into the parent's prune set and deleted it on the transition
upgrade: the exact worker-VM data loss the guard exists to prevent, in the
exact case (migration 54 never ran for this cluster) it was written for.

Refuse when a same-cluster, unpinned MachineDeployment is NOT owned by its
kubernetes-nodes child release (release-name lacks the kubernetes-nodes-<cluster>-
prefix), which catches parent, empty and foreign owners alike while exempting
adopted and natively-created child pools. Add a regression fixture with an
empty release-name that reddens under the old parent-release-name predicate,
and keep every conjunct non-vacuous by mutation.

Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
2026-08-14 20:06:05 +03:00
2025-10-08 09:43:34 +05:00
2025-04-01 18:48:14 +02:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

Open Source Apache-2.0 License Support Active GitHub Release GitHub Commit OpenSSF Best Practices OpenSSF Scorecard

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.

Cozystack user interface

Use-Cases

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.

Languages
Go 52%
Shell 34%
TypeScript 6.8%
Go Template 4.7%
Makefile 1.3%
Other 1.1%