Aleksei Sviridkin
939e6a118d
## What this PR does The dashboard Secret `<release>-credentials` ships with an empty `password` and an empty `uri`, and keeps them for the whole life of the database. `templates/credentials.yaml` resolved the password with `lookup` from `internal-<release>-users`, which the Percona operator creates only after Helm has already rendered the release. The first-install lookup therefore returns nothing, and no later event re-renders a release whose chart and values are unchanged, so the empty values are never repaired. The chart stated this in a comment and in the README, and two unit tests asserted the empty values as intended behaviour. The chart now owns those credentials. It generates the operator's system-user passwords, writes them to the Secret named by `spec.secrets.users`, and fills the dashboard Secret from the same values in the same pass, so the two cannot disagree. Two properties the implementation keeps: - An upgrade never rotates a live password. Every value is reused from the existing Secret when there is one, and generated only when neither the users Secret nor the operator's internal copy holds it. - A database created before this change keeps the Secret the operator generated for it. Ownership is decided by the `meta.helm.sh/release-name` annotation rather than by the Secret's existence, so the chart neither tries to adopt an object Helm did not apply, nor drops it from the manifest on a later upgrade and deletes it. Such a release gets its `<release>-credentials` filled on its next upgrade, with the password the operator had already assigned. Verified on a running v1.6.1 install with the pre-change chart: re-rendering the release filled `password` and `uri` from the operator's existing Secret, the password was not rotated, the pod was not restarted, and those credentials authenticate as `databaseAdmin`. `helm unittest`: 137 tests, 10 suites, all passing. The suite now mocks `lookup` through `kubernetesProvider` for the three branches a fresh render never reaches: a helm-owned users Secret is reused, a Secret the release does not own stays out of the manifest while its password still reaches `<release>-credentials`, and the operator copy rebuilds a missing users Secret. Forcing generation over a live Secret, dropping the operator-copy fallback, or inverting the ownership test each turns the suite red. On the not-owned path a missing password key now fails the render instead of producing a password the users Secret never receives, and the README upgrade section describes the carry-over rather than a rotation. ### Screenshots Not a UI change in this repository. The dashboard renders the Secret as it finds it; only its contents change. ### Downstream repositories Walked the trigger map in `docs/agents/contributing.md` against the diff. The diff touches three files, all under `packages/apps/mongodb`: one template, its test suite, and the package README. No package is added, renamed or removed; `values.yaml` and `values.schema.json` are untouched, so no field, default or version enum moves; no output Secret or Service is renamed, and `<release>-credentials` keeps its name; nothing under `hack/`, `packages/core`, or the `ApplicationDefinition` CRD is involved. The README edit rides the path that is already automated: `mongodb` is in the `APPS` list of the website `Makefile`, so the reference page is regenerated from it on a stable tag. - [x] No downstream repository is affected by this change - [ ] [cozystack/website](https://github.com/cozystack/website) - follow-up: - [ ] [cozystack/terraform-provider-cozystack](https://github.com/cozystack/terraform-provider-cozystack) - follow-up: - [ ] [cozystack/ansible-cozystack](https://github.com/cozystack/ansible-cozystack) - follow-up: - [ ] [cozystack/ccp](https://github.com/cozystack/ccp) - follow-up: - [ ] [cozystack/talm](https://github.com/cozystack/talm) - follow-up: - [ ] [cozystack/cozyhr](https://github.com/cozystack/cozyhr) - follow-up: - [ ] [cozystack/cozy-proxy](https://github.com/cozystack/cozy-proxy) - follow-up: - [ ] [cozystack/cozystack-telemetry-server](https://github.com/cozystack/cozystack-telemetry-server) - follow-up: - [ ] [cozystack/external-apps-example](https://github.com/cozystack/external-apps-example) - follow-up: - [ ] [cozystack/examples](https://github.com/cozystack/examples) - follow-up: ### Release note ```release-note fix(mongodb): the dashboard credentials Secret is now filled on a first install, instead of carrying an empty password and uri until someone runs helm upgrade by hand ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * MongoDB installations now provide usable credentials and connection URIs from the first deployment. * System-user passwords are generated automatically and stored securely. * Existing passwords are preserved during upgrades without rotation. * Connection details support both replica-set and sharded MongoDB deployments. * Credentials include all required system users with generated passwords. * Credential values are restored when an existing users secret is unavailable. * **Documentation** * Updated MongoDB credential documentation to describe automatic generation, secure storage, and upgrade behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.
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 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.