Helm chart installation times out and starts to consume huge amount of CPU about superset HOT 5 OPEN

After running the install with values that override SECRET_KEY it install correctly. So it looks like I misunderstood the guide. But still it says: Default security settings and passwords are included but you SHOULD override those with your own, in particular: but it seems SHOULD should be replace by MUST for it to work and mention it before the install command.

Maybe an explicit mention before the helm install command? Or is it possible to generate it automatically and put it into Kubernetes secrets?

Still, after it install and 10 minutes pass I still see a sharp increase in resource usage and Kubernetes becomes unresponsive:

I will try to play around with the settings of minikube and Docker as there might be some issue there on my side but other charts like MinIO or Grafana didn't cause such problems

EDIT: After re-creating minikube with more resources (8 CPU, 16GB memory) it starts and works normally, can be closed with maybe some update to the Helm install docs

from superset.

it seems SHOULD should be replace by MUST for it to work

I'll open a PR for this... but please feel free to make additional docs PRs or let me know what changes you think need to be made. I'll see the PR to close this issue when merged.

from superset.

@margorczynski please add which version of the Helm chart you're running.

from superset.

It should be the latest considering the command: @villebro

from superset.

From what I see in Kubernetes the superset-init-db job constantly spawns failing pods that fail with the following:

I didn't see any config value to set the secret in the Helm chart. And if it would be required shouldn't the install fail because of a missing parameter?

from superset.