Helm installation uses `latest` tag by default
See original GitHub issueUsing latest
tag in helm releases is really dangerous story. I’ve faced the issue today, because new latest tag expects to have 'dashboards.certifiedBy" column in the table which leads to dashboards fetching error.
It’s much more better to manage app version tag using standard helm approach.
How to reproduce the bug
- Install helm release (current version)
- Go to superset UI
- Will have issue
Expected results
Works
Actual results
Dashboards fetching fails
Screenshots
If applicable, add screenshots to help explain your problem.
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedColumn) column dashboards.certified_by does not exist
LINE 2: ..._position_json, dashboards.css AS dashboards_css, dashboards...
^
[SQL: SELECT count(*) AS count_1
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6
Top Results From Across the Web
Helm Install
It will install the latest stable version of that chart until you specify '--devel' flag to also include development version (alpha, beta, and...
Read more >Using Helm
Helm installs charts into Kubernetes, creating a new release for each installation. And to find new charts, you can search Helm chart repositories....
Read more >Charts - Helm
All charts are loaded by default. If tags or condition fields are present, they will be evaluated and used to control loading for...
Read more >Helm Upgrade
Use 0 for no limit (default 10) --insecure-skip-tls-verify skip tls certificate checks for the chart download -i, --install if a release by this...
Read more >Values Files - Helm
Instructions on how to use the --values flag. ... NAME: geared-marsupi LAST DEPLOYED: Wed Feb 19 23:21:13 2020 NAMESPACE: default STATUS: pending-install ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s still actual
Yes, this is an issue we faced as well. I noticed that the Superset version was frequently getting updated whenever the pods restarted. We have now uploaded an image to ECR and pull from there each time.