[GitHub] [incubator-superset] craig-rueda commented on issue #11363: Helm chart fails completely

[GitBox <gi...@apache.org>]

craig-rueda commented on issue #11363:
URL: https://github.com/apache/incubator-superset/issues/11363#issuecomment-716175968


   I just tried this out and was able to have an installation up in ~2min.
   
   What I tried:
   
   1. Fresh clone
   2. `cd helm/superset`
   3. `helm dependency update`
   4. `helm install superset .`
   
   After a few min, the thing was up :)
   
   Verified by running: `kubectl port-forward svc/superset 8088:8088` and logging into `http://localhost:8080` with `admin/admin`
   
   ```
   $ kubectl get all
   
   NAME                            READY   STATUS      RESTARTS   AGE
   pod/superset-5bdc9554d9-l9cwq   1/1     Running     0          5m27s
   pod/superset-init-db-9jxwh      0/1     Completed   0          5m27s
   pod/superset-postgresql-0       1/1     Running     0          5m27s
   pod/superset-redis-master-0     1/1     Running     0          5m27s
   
   NAME                                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
   service/superset                       NodePort    172.20.60.220    <none>        8088:30817/TCP   5m27s
   service/superset-postgresql            ClusterIP   172.20.216.19    <none>        5432/TCP         5m27s
   service/superset-postgresql-headless   ClusterIP   None             <none>        5432/TCP         5m27s
   service/superset-redis-headless        ClusterIP   None             <none>        6379/TCP         5m27s
   service/superset-redis-master          ClusterIP   172.20.238.102   <none>        6379/TCP         5m27s
   
   NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
   deployment.apps/superset   1/1     1            1           5m27s
   
   NAME                                  DESIRED   CURRENT   READY   AGE
   replicaset.apps/superset-5bdc9554d9   1         1         1       5m27s
   
   NAME                                     READY   AGE
   statefulset.apps/superset-postgresql     1/1     5m27s
   statefulset.apps/superset-redis-master   1/1     5m27s
   
   NAME                         COMPLETIONS   DURATION   AGE
   job.batch/superset-init-db   1/1           101s       5m27s
   ```
   
   @joehoeller - just to be clear around this chart - it's meant to allow for admins to stand up superset (potentially in a production env). We don't make any assumptions about how the thing is configured, nor do we load examples. This is done on purpose as you could imagine that after running Superset for some time, you would not want to re-load examples, etc. on upgrade. Regarding the redis issue you mentioned, I couldn't repro this. Our base Docker image doesn't include any deps like redis, postgres, etc. again on purpose as we don't want to make assumptions, but rather want to encourage people running the thing in their envs to add their own layers for needed drivers. There is a mechanism to add extra deps, which @mistercrunch pointed out above, which added redis correctly :).
   
   


----------------------------------------------------------------
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org