younsl commented on code in PR #475:
URL:
https://github.com/apache/superset-kubernetes-operator/pull/475#discussion_r4354617825
##########
docs/user-guide/configuration.md:
##########
@@ -815,10 +828,12 @@ spec:
fsGroup: 1000
container:
securityContext:
- readOnlyRootFilesystem: true
+ readOnlyRootFilesystem: false
allowPrivilegeEscalation: false
```
+Keep `readOnlyRootFilesystem` unset or `false` for Superset components.
Superset writes to `/tmp` and `/app` at runtime, and Celery beat keeps its pid
and schedule files in `/tmp`.
Review Comment:
Good call, thanks. With an emptyDir at /tmp and readOnlyRootFilesystem set
to true, migrate, init, the web server, worker, and beat all came up on Kind
(login returns 200, worker ping is OK, and writes to /app fail as expected). I
rewrote the note the way you suggested, dropped /app, and removed the redundant
false line in 6eb9b06.
##########
docs/user-guide/installation.md:
##########
@@ -176,6 +176,8 @@ EOF
The operator will create parent-owned lifecycle task Jobs to perform database
migration and initialization, then create the web server Deployment, Service,
and ConfigMap. Check task status with `kubectl describe superset my-superset`.
+The official lean Superset image (e.g. `6.1.0`) has no database drivers. Set
`image` to a build that includes the driver for your connection URI, such as
`psycopg2` for `postgresql+psycopg2`. See
[Metastore](configuration.md#metastore) for driver details.
Review Comment:
Noted, I'll update this when 7.0.0 is out. Aligning the operator version
with the Superset major version once the operator is stable sounds reasonable
to me.
--
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]