Myasnikov Daniil
9f8d6123fd
Second run got past the install, so the backupstrategy-controller fix was right, and the capacity preflight reported what this branch exists to find out: srv1: requests 2440m / allocatable 3950m = 61% srv2: requests 2445m / allocatable 3950m = 61% srv3: requests 2425m / allocatable 3950m = 61% TOTAL: requests 7310m / allocatable 11850m, worst node 61% So -smp 4 schedules the lean platform with room to spare, evenly balanced, and `Insufficient cpu` never appears. It then failed in the OpenAPI step, at "Test kinds", which reads .items[0].kind from /apis/apps.cozystack.io/v1alpha1/ingresses and got null because turning ingress off on the root Tenant means no Ingress instance exists. That assertion is about the aggregated API returning typed kinds for list items and has nothing to do with capacity, so the fix is to give it an instance rather than to weaken it: ingress goes back on, and the HR waits name it again. It costs about 310m for the NGINX controller and its default backend, against 39 points of headroom, so the experiment is unaffected. monitoring and seaweedfs stay off, which is where the bulk of the tenant-root workload was. Checked the rest of that file for the same shape: "Test kinds" is the only place an app instance is required, and the only two kinds it reads are tenants and ingresses. Nothing in it references monitoring, seaweedfs, bucket, grafana, velero, goldpinger or backupstrategy. Assisted-By: Claude <noreply@anthropic.com> 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.