villebro opened a new pull request, #93:
URL: https://github.com/apache/superset-kubernetes-operator/pull/93
## Summary
This PR applies the final release-readiness cleanup from the Helm chart
parity and security audit. It tightens the operator’s CRD contract around
managed Kubernetes connectivity, adds the remaining Helm-compatible escape
hatch for bootstrap scripts, and updates the docs so production users have a
clear boundary between operator-managed fields and Superset-owned Python
configuration.
## Details
- Adds `spec.metastore.driver` so structured PostgreSQL/MySQL connections
can select the SQLAlchemy driver.
- PostgreSQL defaults to `psycopg2`.
- MySQL defaults to `mysqldb`.
- Adds `bootstrapScript` support.
- Top-level `spec.bootstrapScript`.
- Per-component overrides for Python components.
- Lifecycle override for `migrate`, `rotate`, and `init`.
- Included in config/checksum handling so changes roll the affected
workloads.
- Websocket and clone tasks are intentionally excluded.
- Simplifies Celery app configuration.
- Removes the top-level `spec.celery` app-config API.
- The operator now renders only Celery connectivity derived from
`spec.valkey`: broker URL, result backend URL, and SSL settings.
- Celery application behavior such as imports, task annotations, routes,
beat schedules, and scheduler expiration is documented as explicit Python
config owned by the Superset admin.
- User guide recommends placing Beat-only `beat_schedule` config under
`spec.celeryBeat.config` to avoid recycling unrelated components.
- Improves ServiceMonitor self-healing by registering a dynamic watch when
the ServiceMonitor CRD exists at manager startup.
- Updates release/security docs.
- Trims `SECURITY.md` into a minimal gateway.
- Expands `docs/reference/security.md` with trusted raw Python and
bootstrap-script caveats.
- Updates configuration, architecture, migration, and API reference docs.
- Adds PR title length guidance: aim for 50 characters and avoid exceeding
72.
--
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]
