Andrey Kolkov
7abb7eccd6
Backport of #3333 onto release-1.5. spec.components.platform.values.backupStorage on the cozystack.cozystack-platform Package -- the documented override path for the cozy-default BackupClass -- never reached the backupstrategy-controller HelmRelease, so endpoint/region/bucketName overrides for an external S3 were silently dropped (#3245). The platform chart now forwards the block into the emitted child Package the same way bundles/iaas.yaml forwards kubevirt and gpu-operator values. The 4-arg cozystack.platform.package helper the change needs already exists on this branch. Two conflicts, both from unrelated drift in the touched files rather than from the fix: * platform values.yaml -- main's hunk carries `monitoring.rootEnabled` alongside `backupStorage`. That key belongs to the tenant-root monitoring gate (#3181), which is not on release-1.5 and whose absence nothing here depends on, so only the backupStorage block is taken. * docs/operations/backup-classes.md -- the conflicting hunk rewrites the Postgres upgrade note for the CNPG barman plugin migration (spec.plugins + ObjectStore), which is 1.6 behaviour. release-1.5 still renders spec.backup.barmanObjectStore, so this branch keeps its own prose. The rest of the doc update applied cleanly and was checked claim-by-claim against this branch rather than assumed: the helmrelease-interval flag, the cozy-backup-controller namespace, the cozystack_backup_credentials_projection_* metric names and the provisionBucket / namespace / bucketName knobs the new table rows describe all exist here. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com> (cherry picked from commit 13aa3cb31e71f89e6ffe2a5fcd0fcd9e3f80e970)
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 Feature Requests please use the Discussion's Feature Request section.
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.