Open mcopik opened 2 years ago
Could my issue be a duplicate of #701?
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.
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?
I think it's the same issue as https://github.com/apache/openwhisk-deploy-kube/issues/528.
Is there any idea how to solve the problem for now?
Hi!
I've been following the documentation on how to set up OpenWhisk with a private Docker registry. 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: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:
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.