Wire redis into the engine-agnostic CA extraction contract so a tenant can verify the Redis server without being handed private key material. Use the declared source rather than labelling the chart's CA Certificate. The operator fork already reconciles a key-free Opaque Secret holding nothing but the ca.crt it lifts out of the release TLS Secret, and naming that as the source is strictly better than the label route: no private key ever sits beside the object the projection reads from. The cert-manager Secret that does hold the CA key is not referenced here at all. The include selector matching the tenant-ca label is what makes the lineage webhook mark the projection as a tenant resource, which is what the tenant-secrets registry gates on. The selector is deliberately specific — an empty one resolves to labels.Everything() and would mark every Secret in the namespace. Because that selector matches on the label alone with no name constraint, add an exclude backstop naming the two release-owned Secrets that carry private keys. Exclude is evaluated before include, so a name listed there cannot be promoted whatever labels it acquires. The comment states the bound honestly: matching is exact-name with no globs, so Secrets a future operator version introduces are not covered, and the primary defence stays the controller stamping the label only on its own projection. This is inert until the CA-extraction controller merges. The ApplicationDefinition CRD has no caCert field yet, so the block is pruned on apply and no projection exists for the include to select. Signed-off-by: Aleksei Sviridkin <f@lex.la> Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
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.
