dmitrynovik opened a new issue, #36414:
URL: https://github.com/apache/superset/issues/36414

   ### Bug description
   
   1. Download `values.yaml` from 
https://github.com/apache/superset/blob/master/helm/superset/values.yaml
   2. Run ` helm upgrade --install --values values.yaml superset 
superset/superset` as 
[described](https://superset.apache.org/docs/installation/installation-methods#kubernetes-k8s)
 
   
   Expected: default installation works
   Actual: image pull errors for redis and postgres
   ```
   superset-6cfd5b6684-k9699          0/1     Init:0/1           16 (5m9s ago)  
  18h
   superset-init-db-c7bch             0/1     Init:Error         0              
  3m28s
   superset-init-db-czrtf             0/1     Init:0/1           0              
  96s
   superset-init-db-pt2f6             0/1     Init:Error         0              
  5m20s
   superset-postgresql-0              0/1     ImagePullBackOff   0              
  30m
   superset-redis-master-0            0/1     ImagePullBackOff   0              
  30m
   superset-worker-78c4d4fbd6-zbdg8   0/1     Init:0/1           16 (5m19s ago) 
  18h
   ``` 
   
   ```
   kubectl describe pod superset-redis-master-0 | grep -i image
       Image:         docker.io/bitnami/redis:7.0.10-debian-11-r4
       Image ID:
         Reason:       ImagePullBackOff
     Normal   Pulling    31m (x4 over 32m)    kubelet            Pulling image 
"docker.io/bitnami/redis:7.0.10-debian-11-r4"
     Warning  Failed     31m (x4 over 32m)    kubelet            Failed to pull 
image "docker.io/bitnami/redis:7.0.10-debian-11-r4": rpc error: code = NotFound 
desc = failed to pull and unpack image 
"docker.io/bitnami/redis:7.0.10-debian-11-r4": failed to resolve reference 
"docker.io/bitnami/redis:7.0.10-debian-11-r4": 
docker.io/bitnami/redis:7.0.10-debian-11-r4: not found
     Warning  Failed     31m (x4 over 32m)    kubelet            Error: 
ErrImagePull
     Warning  Failed     30m (x6 over 32m)    kubelet            Error: 
ImagePullBackOff
     Normal   BackOff    19s (x152 over 32m)  kubelet            Back-off 
pulling image "docker.io/bitnami/
   ```
   
   ```
    kubectl describe pod superset-postgresql-0 | grep -i image
       Image:           docker.io/bitnami/postgresql:14.17.0-debian-12-r3
       Image ID:
         Reason:        ImagePullBackOff
     Normal   Pulling    32m (x4 over 34m)     kubelet            Pulling image 
"docker.io/bitnami/postgresql:14.17.0-debian-12-r3"
     Warning  Failed     32m (x4 over 34m)     kubelet            Failed to 
pull image "docker.io/bitnami/postgresql:14.17.0-debian-12-r3": rpc error: code 
= NotFound desc = failed to pull and unpack image 
"docker.io/bitnami/postgresql:14.17.0-debian-12-r3": failed to resolve 
reference "docker.io/bitnami/postgresql:14.17.0-debian-12-r3": 
docker.io/bitnami/postgresql:14.17.0-debian-12-r3: not found
     Warning  Failed     32m (x4 over 34m)     kubelet            Error: 
ErrImagePull
     Warning  Failed     32m (x6 over 34m)     kubelet            Error: 
ImagePullBackOff
     Normal   BackOff    106s (x151 over 34m)  kubelet            Back-off 
pulling image "docker.io/bitnami/postgresql:14.17.0-debian-12-r3"
   ````
   
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to