villebro opened a new pull request, #95:
URL: https://github.com/apache/superset-kubernetes-operator/pull/95

   ## Summary
   
   Pre-release cleanup surfaced by a full release-readiness audit ahead of the 
0.1.0 vote. The audit found the codebase, Helm-chart feature parity, and 
security posture all in good shape with no release blockers — this PR fixes 
only the genuine loose ends it turned up. All changes are 
documentation/cosmetic; there are no code or API changes.
   
   The headline non-issue worth recording: the `0.0.0-dev` strings in 
`Makefile` and `Chart.yaml` are intentional placeholders that 
`scripts/release-rc.sh` auto-bumps from its `<version>` argument, so they are 
not release blockers.
   
   ## Details
   
   - **`docs/getting-started.md`** — the Helm install example hardcoded 
`--version 0.0.0-dev`, which is never a published chart version and was 
inconsistent with `README.md`, `installation.md`, and `downloads.md`. Replaced 
with a `<version>` placeholder plus a pointer to Downloads.
   - **`docs/reference/security.md`** — corrected an inaccuracy in the RBAC 
justification table. It collapsed `supersets` + `supersets/status` into one row 
that read as though the operator can `update`/`patch` the CR spec. The actual 
grants are `get;list;watch` on `supersets` and `get;update;patch` on 
`supersets/status` only; split into two rows. Also added the missing `update` 
verb on `events` to match the generated `role.yaml`.
   - **`config/prometheus/monitor.yaml`** — reworded the leftover kubebuilder 
scaffold `TODO(user):` comment into intentional guidance, keeping the 
`insecureSkipVerify` rationale and the cert-manager patch pointer.
   - **Superset image tag refresh** (`6.0.1` → `6.1.0`) across the docs 
examples and the production sample.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to