You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2022/01/24 23:35:33 UTC

[GitHub] [openwhisk-deploy-kube] mcopik opened a new issue #721: Incomplete deployment with private Docker registry

mcopik opened a new issue #721:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/721


   Hi!
   
   I've been following the documentation on [how to set up OpenWhisk with a private Docker registry](https://github.com/apache/openwhisk-deploy-kube/blob/master/docs/private-docker-registry.md). After configuring authorization with a self-signed certificate, which works fine, and finding out all versions of images that need to be transported to the private registry, I got the deployment with `helm` almost ready. Everything seems to be deployed except for invoker pods:
   
   ```
   openwhisk            owdev-alarmprovider-85c6cb4f6d-gsfnz                         1/1     Running            0          3m54s
   openwhisk            owdev-apigateway-64c77ddb4-2gvr8                             1/1     Running            0          3m54s
   openwhisk            owdev-controller-0                                           1/1     Running            0          3m54s
   openwhisk            owdev-couchdb-d75b8cf5c-xlxz5                                1/1     Running            0          3m54s
   openwhisk            owdev-gen-certs-6tpbz                                        0/1     Completed          0          3m54s
   openwhisk            owdev-init-couchdb-7cqtq                                     0/1     Completed          0          3m54s
   openwhisk            owdev-install-packages-fhg2l                                 0/1     Init:0/1           0          3m54s
   openwhisk            owdev-invoker-0                                              1/1     Running            0          3m54s
   openwhisk            owdev-kafka-0                                                1/1     Running            0          3m54s
   openwhisk            owdev-kafkaprovider-696dcc45f9-24m4c                         1/1     Running            0          3m54s
   openwhisk            owdev-nginx-65775cb5d6-zzsng                                 1/1     Running            0          3m54s
   openwhisk            owdev-redis-7775bb848f-f2twc                                 1/1     Running            0          3m54s
   openwhisk            owdev-seccomp-6q9cd                                          1/1     Running            0          3m54s
   openwhisk            owdev-seccomp-n5x8m                                          1/1     Running            0          3m54s
   openwhisk            owdev-wskadmin                                               1/1     Running            0          3m54s
   openwhisk            owdev-zookeeper-0                                            1/1     Running            0          3m54s
   openwhisk            wskowdev-invoker-00-6-whisksystem-invokerhealthtestaction0   0/1     ErrImagePull       0          40s
   openwhisk            wskowdev-invoker-00-7-prewarm-nodejs14                       0/1     ErrImagePull       0          39s
   ```
   
   A closer inspection suggests that pods are not authorized to access the registry and it does not look like any certificate and network availability issue, but an incorrect/missing authorization:
   
   ```
   Events:
     Type     Reason     Age                From               Message
     ----     ------     ----               ----               -------
     Normal   Scheduled  31s                default-scheduler  Successfully assigned openwhisk/wskowdev-invoker-00-1-prewarm-nodejs14 to kind-worker2
     Normal   Pulling    16s (x2 over 30s)  kubelet            Pulling image "192.168.0.19:5000/openwhisk/action-nodejs-v14:1.19.0"
     Warning  Failed     16s (x2 over 30s)  kubelet            Failed to pull image "192.168.0.19:5000/openwhisk/action-nodejs-v14:1.19.0": rpc error: code = Unknown desc = failed to pull and unpack image "192.168.0.19:5000/openwhisk/action-nodejs-v14:1.19.0": failed to resolve reference "192.168.0.19:5000/openwhisk/action-nodejs-v14:1.19.0": unexpected status code [manifests 1.19.0]: 401 Unauthorized
     Warning  Failed     16s (x2 over 30s)  kubelet            Error: ErrImagePull
     Normal   BackOff    3s (x2 over 29s)   kubelet            Back-off pulling image "192.168.0.19:5000/openwhisk/action-nodejs-v14:1.19.0"
     Warning  Failed     3s (x2 over 29s)   kubelet            Error: ImagePullBackOff
   ```
   
   I'm not using any custom images and I have not even tried to create any actions - this is also from standard deployment. The image is available in my registry. Does it look like there's a missing docker login on these pods?
   
   I am using OpenWhisk with helm 3.8 and kind 0.11.


-- 
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: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk-deploy-kube] mcopik commented on issue #721: Incomplete deployment with private Docker registry

Posted by GitBox <gi...@apache.org>.
mcopik commented on issue #721:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/721#issuecomment-1021174387


   Could my issue be a duplicate of #701?


-- 
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: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk-deploy-kube] IsaacNez commented on issue #721: Incomplete deployment with private Docker registry

Posted by GitBox <gi...@apache.org>.
IsaacNez commented on issue #721:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/721#issuecomment-1069284006


   Hi!
   
   I saw one of your comments to propagate the ```imagePullSecret``` using ```pod-template``` but I cannot find how to define this template since the action pods seem to not be defined as a regular one, e.g, invoker or controller. Is that correct?


-- 
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: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk-deploy-kube] mcopik commented on issue #721: Incomplete deployment with private Docker registry

Posted by GitBox <gi...@apache.org>.
mcopik commented on issue #721:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/721#issuecomment-1021174387


   Could my issue be a duplicate of #701?


-- 
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: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [openwhisk-deploy-kube] dgrove-oss commented on issue #721: Incomplete deployment with private Docker registry

Posted by GitBox <gi...@apache.org>.
dgrove-oss commented on issue #721:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/721#issuecomment-1021647395


   Hi.  Yes, I think you are getting hit with the same problem.  We need to propagate the imagePullSecret into the pod template that is being used by the invoker when it asks Kubernetes to create pods for running functions.


-- 
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: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org