Aleksei Sviridkin 5713b9774e fix(foundationdb): let tenant roles read the connection ConfigMap (#4148)
A tenant cannot connect to its own FoundationDB: the
fdb-kubernetes-operator writes the cluster file into the
`<release>-config` ConfigMap, but tenant subjects have no RBAC to read
it and the dashboard resource map does not expose it, so there is no way
to obtain the connection string without cluster-admin access.

This PR:

- adds `<release>-config` to the dashboard resource map;
- adds a Role/RoleBinding granting get/list/watch on exactly that
ConfigMap to the tenant `use` access level (via the existing cozy-lib
helper);
- adds helm unittest coverage (`make test`, 6 tests).

Out of scope: FoundationDB currently exposes no Service, so clients
still need in-cluster reachability to the coordinator pod IPs from the
cluster file — that is a separate topic.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **New Features**
* Added the FoundationDB configuration resource to the dashboard
resource map.
* Added read-only access for authorized tenant users and service
accounts to view the configuration resource.
* **Bug Fixes**
* Ensured configuration access and resource visibility remain available
when monitoring is disabled.
* **Tests**
* Added coverage to verify resource mapping, access permissions, and
rendered chart output.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-09-18 11:57:37 +04:00
2025-10-08 09:43:34 +05:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

GitHub Release Apache-2.0 License Commit activity OpenSSF Best Practices OpenSSF Scorecard CLOMonitor Support

Cozystack

Cozystack is a free and open-source platform and framework for building clouds.

Cozystack is a CNCF Sandbox 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.

Cozystack user interface

Use-Cases

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 are welcome to take on the fix yourself. 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 us in #cozystack, on either CNCF Slack (get an invite) or Kubernetes Slack (get an invite), in our Telegram group, and at our community meetings. Add them to your Google Calendar or iCal for convenience.

Project documents

Document What it covers
Governance How decisions are made and who makes them
Contributor Ladder How to grow from contributor to maintainer
Maintainers Who maintains the project
Code of Conduct What we expect of each other
Security Policy Reporting a vulnerability, and which releases get fixes
Adopters Who runs Cozystack in production
Roadmap Where the project is going

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.

Languages
Go 47.2%
Shell 37.6%
TypeScript 7%
Go Template 5.4%
Makefile 1.4%
Other 1.2%