-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add imagePullSecrets to PodTemplate #1779
Comments
On further consideration I don't think we urgently need this, since you can already add pull secrets to the SA that runs the Pod. |
we have a similar issue, want to have this feature. I have opened an issue on tekton 2339 |
/reopen |
@skaegi: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@skaegi @afrittoli please take a look |
If it is fine I will look at this and try to make a PR today for it later this evening :) Have you started on this @skaegi ? |
Thanks @NikeNano for adding this feature. I think this issue can be closed. |
/close |
@vdemeester: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
In K8s, Pods can specify a
imagePullSecrets
which identifies K8s secrets that the container runtime should use to authorize container image pulls when starting a Pod (K8s docs). This potentially provides creds to the container runtime (docker, containerd, etc.) in cases when the image is not publicly available.This isn't exposed in a TaskRun's
podTemplate
(PodTemplate
type), to be added to the underlying Pod's configuration.Exposing this would allow Tekton users to declare K8s secrets that should be used to pull images specified in
steps
./kind feature
/area api
The text was updated successfully, but these errors were encountered: