Redis and Sentinel read tls-cert-file and tls-key-file once at startup, so a leaf renewed by cert-manager 30 days before its one-year expiry is served only after the pods restart. The operator does that restart: on every reconcile it reads the TLS Secret and stamps a hash of tls.crt and ca.crt into the pod template of the Redis StatefulSet and the Sentinel Deployment, so a renewal rolls Redis through the operator's own roller (the StatefulSet is OnDelete; the roller replaces one pod per reconcile, replicas before the master) and Sentinel through its Deployment. The TLS section presented the setup as turnkey and said nothing about renewal. Say what happens, and name the fallback: when the roll cannot run, because the operator is down or its reconcile of this RedisFailover keeps failing, the deadline is the old certificate's expiry, since past it the operator's own TLS connections to Sentinel and Redis fail along with the clients. The CA has a clock of its own: five years, reissued on the same key before the end, so a ca.crt copied once verifies new leaves only until the original CA certificate expires. Say that too, and point at re-reading the projection instead of baking the copy in. A stakater reloader annotation is not an alternative here and is not used: the operator regenerates the pod template on every reconcile, so nothing written into it from outside survives to the next one. 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.
