villebro opened a new pull request, #105: URL: https://github.com/apache/superset-kubernetes-operator/pull/105
## Summary The Helm-to-operator migration guide buried its feature comparison at the bottom of the page, and what comparison existed was split across a high-level table and two bullet lists. For a Helm user deciding whether to adopt the operator, that comparison is the most important content in the document. This PR replaces the scattered pieces with a single, prominent **Helm Chart vs. Operator** table near the top, grouped into Application & configuration, Routing, Lifecycle, Scaling & operations, and Dependencies & secrets so it stays scannable while holding every differentiating feature in one place. The wording is aimed at a current Helm user weighing the move — factual, no overselling. It also surfaces operator base-functionality wins, splits lifecycle into per-task detail in the value mapping, and closes a few coverage gaps a real migration would hit. ## Details - **Single consolidated comparison.** One grouped table replaces the former at-a-glance table and the "What you gain" / "Intentional differences" bullet lists, followed by a short note pointing to the workarounds for the intentional gaps. The old bottom "Operator Differences and Parity Gaps" section is removed. - **Base-functionality rows.** Added rows for the layered `superset_config.py` (operator-generated base + appendable top-level and per-component `config`) and the auto-applied, override-protected `app.kubernetes.io/*` + `superset.apache.org/parent` labels — both verified against the renderer and label helpers. - **Routing difference made explicit.** The chart's Ingress fronts only the web server (websocket via a separate rule); the operator fans out to every present component on its own subpath from one object, for both Ingress and Gateway API. - **Lifecycle as a value-mapping subsection.** Pulled lifecycle into a dedicated `Lifecycle Tasks` table with one row per task (clone, migrate, rotate, init), documenting drain behavior, gating, triggers, and environment restrictions. Clone is framed as a Development/Staging staging-data tool (destructive, `cronSchedule` refresh) and explicitly not a production backup. - **Ingress TLS + loadBalancerIP.** Added a concrete `spec.networking.ingress.tls` example and a provider-annotation alternative for `service.loadBalancerIP`. No field-name corrections were required: an audit confirmed every spec path the guide references already exists as documented. `mkdocs build --strict` passes. -- 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]
