Bug description
I use apache superset helm charts(version 0.15.0 with superset version 5.0.0) to deploy superset in my air-gap environment.
Before I deploy superset, I have deploy my own map service using osm-tile-server successfully in air-gap environment.
And I can see map using firefox with url 'http://
Then, I deploy superset. I define custom value in value.yaml which is in the helm chart. My define is like below:
configOverrides:
map: |
DECKGL_BASE_MAP = [
['tile://https://<my-ip>/tile/{z}/{x}/{y}.png', 'MyTile']
]
from flask_cors import CORS
ENABLE_CORS = True
from typing import Any
CORS_OPTIONS: dict[Any, Any] = {
"origins": [
"http://<my-ip>/tile/{z}/{x}/{y}.png",
]
}
TALISMAN_CONFIG = {
"content_security_policy": {
"connect-src": [
"'self'",
"https://<my-ip>/tile/{z}/{x}/{y}.png",
]
}
secret: |
SECRET_KEY = '...' # Here I define and with no display here
I add two 'from xxx import xxx', because the log describe they needed. Then I install with command below:
helm install superset -n test -f value.yaml ./superset-0.15.0.tgz
With kubectl port-forward command, I can not see anything.
But when cut the map reference like below:
configOverrides:
map: |
DECKGL_BASE_MAP = [
['tile://https://<my-ip>/tile/{z}/{x}/{y}.png', 'MyTile']
]
secret: |
SECRET_KEY = '...' # Here I define and with no display here
I can access superset web page, but no map to be displayed.
Screenshots/recordings
No response
Superset version
5.0.0
Python version
I don't know
Node version
I don't know
Browser
Firefox
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
Hi @thuanghai! I'm Dosu and I’m helping the superset team.
Superset 5.0.0 does not support custom map tile providers for deck.gl charts via the DECKGL_BASE_MAP
setting—only Mapbox (via MAPBOX_API_KEY
) is supported. There is no code path in the backend or frontend that uses DECKGL_BASE_MAP
, so any configuration changes to this variable will have no effect, and a blank map is expected in this scenario. This is a product limitation, not a misconfiguration or CORS/CSP issue. If you need offline/air-gap map support, you may need to explore workarounds such as using Mapbox with a local tile server (if possible) or consider other visualization types that support custom tiles. If custom tile provider support is critical for your use case, you may want to follow Superset's roadmap for future updates or request this as a feature.
Reference: code and documentation analysis
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other