-
Notifications
You must be signed in to change notification settings - Fork 61
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
Support for an image pull secret in the NFS Server pods #113
Comments
8 tasks
g-linville
added a commit
to g-linville/dynamic-nfs-provisioner
that referenced
this issue
Sep 21, 2021
…ve#114 Adds support for setting an image pull secret on the NFS Server pods. Signed-off-by: Grant Linville <[email protected]>
8 tasks
g-linville
added a commit
to g-linville/dynamic-nfs-provisioner
that referenced
this issue
Sep 22, 2021
…ve#114 Adds support for setting an image pull secret on the NFS Server pods. Signed-off-by: Grant Linville <[email protected]>
8 tasks
mynktl
pushed a commit
that referenced
this issue
Nov 11, 2021
Adds support for setting an image pull secret on the NFS Server pods. Signed-off-by: Grant Linville <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem/challenge you have
I want to pull the NFS Server container image from a private container registry, but cannot do it because the image pull secret used by the provisioner is not passed along to the NFS servers it creates.
Describe the solution you'd like
I would like an additional value in the Helm chart which allows me to specify an image pull secret to be used by the NFS servers, so that the NFS servers in Kubernetes can use container images that are from a private registry.
Anything else you would like to add:
I will begin working on this myself, but thought I should document it here.
Environment:
kubectl get po -n openebs --show-labels
): 0.7.1kubectl version
): 1.21.4cat /etc/os-release
): Pop!_OS 21.04uname -a
): 5.13.0-7614-genericVote on this issue!
This is an invitation to the OpenEBS community to vote on issues.
Use the "reaction smiley face" up to the right of this comment to vote.
The text was updated successfully, but these errors were encountered: