maikokuppe opened a new pull request #14349: URL: https://github.com/apache/superset/pull/14349
### SUMMARY It is recommended to build one's own docker image when using superset on production. However a custom docker image contains confidential information, e.g. the `SECRET_KEY` configuration value. Thus it is necessary to use a docker image hosted in a private registry. Access credentials to a private docker registry are usually provided to Kubernetes via the `imagePullSecrets` field, which references to a secret containing the credentials. This PR makes it possible to configure this via the `values.yaml`. ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF none ### TEST PLAN none ### ADDITIONAL INFORMATION - [ ] Has associated issue: - [ ] Changes UI - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351)) - [ ] Migration is atomic, supports rollback & is backwards-compatible - [ ] Confirm DB migration upgrade and downgrade tested - [ ] Runtime estimates and downtime expectations provided - [x] Introduces new feature or API - [ ] Removes existing feature or API -- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
