在Rancher Kubernetes环境中安装Apache Superset遇到问题

环境信息 #

• Redis版本: 18.16.1
• PostgreSQL版本: 14.2.3
• Helm版本: 3.14.1
• Kubernetes环境: k3s

问题详情 #

执行以下命令安装Superset Helm Chart（版本0.12.6）：

helm install my-superset superset/superset --version 0.12.6

命令执行耗时极长，最终返回错误：

Error: INSTALLATION FAILED: failed post-install: 1 error occurred:
        * timed out waiting for the condition

Pod状态 #

执行kubectl get pods查看状态，多个Pod处于错误/崩溃重启状态：

C:\Users\Comarch>kubectl get pods
NAME                                  READY   STATUS             RESTARTS      AGE
my-redis-master-0                     1/1     Running            0             11m
my-redis-replicas-0                   1/1     Running            0             11m
my-postgresql-0                       1/1     Running            0             11m
my-redis-replicas-1                   1/1     Running            0             11m
my-redis-replicas-2                   1/1     Running            0             10m
my-superset-postgresql-0              1/1     Running            0             7m4s
my-superset-init-db-mhqpn             0/1     Error              0             7m4s
my-superset-redis-master-0            1/1     Running            0             7m4s
my-superset-init-db-s8g6z             0/1     Error              0             6m34s
my-superset-init-db-6kngd             0/1     Error              0             6m8s
my-superset-init-db-tjvtf             0/1     Error              0             5m23s
my-superset-init-db-27x6z             0/1     Error              0             3m57s
my-superset-init-db-tndb6             0/1     Error              0             72s
my-superset-7449574d54-fvlgf          0/1     Running            1 (63s ago)   7m4s
my-superset-worker-85b4c79494-fqg8c   0/1     CrashLoopBackOff   6 (14s ago)   7m4s

相关日志片段 #

k3s日志

I0226 14:08:35.678505    1224 scope.go:117] "RemoveContainer" containerID="e364b25e0b28f773a7bcd14d8f3092ddb9663b9a80e37f82b1a52551e74feba4"
E0226 14:08:35.680011    1224 pod_workers.go:1298] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"superset\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=superset pod=my-superset-worker-85b4c79494-fqg8c_default(102794ea-195f-414a-a218-ec474173736c)\"" pod="default/my-superset-worker-85b4c79494-fqg8c" podUID="102794ea-195f-414a-a218-ec474173736c"

Docker日志

time="2024-02-26T14:09:32.963550813Z" level=error msg="collecting stats for 41bce38aca76aea4d7f668ca38619991711f7210030e187799f424a5ed46d697: no metrics received"
time="2024-02-26T14:09:33.218075523Z" level=error msg="loading cgroup for 106958" error="cgroups: cannot find cgroup mount destination"

Superset Pod核心日志

--------------------------------------------------------------------------------
                                    WARNING
--------------------------------------------------------------------------------
A Default SECRET_KEY was detected, please use superset_config.py to override it.
Use a strong complex alphanumeric string and use a tool to help you generate
a sufficiently random sequence, ex: openssl rand -base64 42
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Refusing to start due to insecure SECRET_KEY
[2024-02-26 14:16:31 +0000] [634] [INFO] Worker exiting (pid: 634)
Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
[2024-02-26 14:16:32 +0000] [8] [ERROR] Worker (pid:634) exited with code 1
[2024-02-26 14:16:32 +0000] [8] [ERROR] Worker (pid:634) exited with code 1.
[2024-02-26 14:16:32 +0000] [659] [INFO] Booting worker with pid: 659

已尝试操作 #

• 更换Redis、PostgreSQL版本
• 使用自定义my_values.yaml配置文件
  以上操作均未解决问题，寻求技术支持。

内容的提问来源于stack exchange，提问作者Karol