0.12.11 fails for helm install about superset HOT 2 CLOSED

Hello @tanmaykansara! I'm here to assist you with any bugs, questions, or contributions related to the Superset repository. Let's tackle this issue together!

To resolve the Helm upgrade failure and the pip dependency conflict when installing Superset, you can follow these steps:

1. Helm Upgrade Failure:

   • Ensure that the initContainers are correctly configured to wait for the necessary services (PostgreSQL and Redis) to be ready before proceeding with the Superset initialization. You can refer to the initContainers configuration in the values.yaml file.
   • Verify that the forceReload option is set to true if you want to force the deployment to reload on each upgrade.

2. Pip Dependency Conflict:

   • Modify the bootstrapScript to handle pip dependencies explicitly. You can add a step to install the required pip packages with specific versions to avoid conflicts.

Here is an example of how you can modify the values.yaml to address these issues:

supersetNode:
  forceReload: true
  initContainers:
    - name: wait-for-postgres
      image: "{{ .Values.initImage.repository }}:{{ .Values.initImage.tag }}"
      imagePullPolicy: "{{ .Values.initImage.pullPolicy }}"
      envFrom:
        - secretRef:
            name: "{{ tpl .Values.envFromSecret . }}"
      command:
        - /bin/sh
        - -c
        - dockerize -wait "tcp://$DB_HOST:$DB_PORT" -timeout 120s

bootstrapScript: |
  #!/bin/bash
  if [ ! -f ~/bootstrap ]; then
    echo "Running Superset with uid {{ .Values.runAsUser }}" > ~/bootstrap
    # Install specific pip packages to avoid conflicts
    pip install --upgrade pip
    pip install cryptography==42.0.4
  fi

By ensuring the initContainers wait for the necessary services and explicitly handling pip dependencies in the bootstrapScript, you can mitigate the Helm upgrade failure and pip dependency conflict issues ^[1][2].

To continue talking to Dosu, mention @dosu.

from superset.

Ty for this.

from superset.