Several comments described a shape the chart does not render. A test comment claimed the chart carries a management cacertfile while the assertion directly below it pins that no additionalConfig exists at all; the suite title and two section headers advertised a management HTTPS block that is never rendered; and a scope note named interNodeTLS, which is not a field on RabbitmqCluster — the CRD exposes exactly secretName, caSecretName and disableNonTLSListeners. Two tests were named for something they did not assert. The inter-node scope test checked disableNonTLSListeners, which by this chart's own reasoning has no bearing on port 25672; it now checks caSecretName, which is the field that would actually configure inter-node mTLS. State the ResourceDefinition backstop's real standing. The exclude list is defence in depth, not the first line: promotion runs on the tenantresource label that the lineage webhook stamps only when it resolves an ancestor, and a cert-manager Secret has no ownerReference or Helm metadata, so it fails closed before include or exclude is consulted. The list covers the case where that stops holding. Pin the dashboard Role's complete grant rather than only the absence of known-bad names — every existing assertion there was a notContains, so a Role that gained an unrelated Secret satisfied all of them. Record what upgrading an existing external instance does: tls.enabled inherits external, so the broker pods roll once when the operator mounts the new Secret, and the instance gains a cert-manager dependency. No client breaks, but a stateful broker restarting is not something to discover from a diff. Drop four tests that duplicated earlier ones verbatim. Assisted-by: LLM 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.
