-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Image Registry #354
Comments
Same issue for the
however the
|
Also having this issue, we're looking to migrate from the Pure Storage Orchestrator CSI driver and this is blocking us from deploying this operator, @piyush-nimbalkar apologies for the ping, this issue has been open for a while. |
Sorry guys for the late response. This just slipped my radar. You can add
|
How can the default pause container image used for the portworx-api and portworx-kvdb pods be overridden? I have specified a custom image registry in the install spec which works for just about everything else but for the pause container it appends the original registry and image path as follows: -
Back-off pulling image "docker.repo/k8s.gcr.io/pause:3.1"
I need it to be: -
docker.repo/pause:3.1
I have tried to edit and update the portworx-api DaemonSet but it then reverts back to the original so I am guess the operator is resetting it.
Found this which suggests adding // to the custom registry path which fixes the pause container pull but then breaks everything else: -
#319
The text was updated successfully, but these errors were encountered: