Teach the aggregated apiserver to serve application kinds in any API group registered through an ApplicationGroupDefinition, instead of hardwiring apps.cozystack.io everywhere: - config.ApplicationConfig carries the resolved group; the startup loading path (extracted into buildResourceConfig, now unit-testable) lists ApplicationGroupDefinitions next to ApplicationDefinitions and resolves each definition's group. A definition referencing an unregistered group (dangling reference) is skipped with an error log and picked up again once the group is registered; kinds must stay unique across groups because OpenAPI schema refs are keyed by kind. - RegisterDynamicTypes registers kinds in their selected group and registers each non-default group-version (meta types, priority) the way install.Install does for the default group. - The apiserver installs one APIGroupInfo per group; the default group is always installed so its static APIService stays healthy. - The REST storage derives gvr/gvk (and hence the HelmRelease application.group label and every label-selector check) from the configured group. - OpenAPI post-processors stamp each kind with its group; the v3 processor runs per group-version document and only clones the kinds of that document's group (derived from its paths). ApplicationDefinitions with no group keep today's behavior bit for bit; group pickup is restart-based via the existing config-hash rollout (no hot reload yet). Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Timofei Larkin <lllamnyp@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.
