Skip to content
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

Closed
imjasonh opened this issue Dec 19, 2019 · 9 comments
Closed

Add imagePullSecrets to PodTemplate #1779

imjasonh opened this issue Dec 19, 2019 · 9 comments
Assignees
Labels
area/api Indicates an issue or PR that deals with the API. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@imjasonh
Copy link
Member

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

@imjasonh imjasonh added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Dec 19, 2019
@tekton-robot tekton-robot added kind/feature Categorizes issue or PR as related to a new feature. area/api Indicates an issue or PR that deals with the API. labels Dec 19, 2019
@imjasonh
Copy link
Member Author

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.

@kevinyu98
Copy link

we have a similar issue, want to have this feature. I have opened an issue on tekton 2339

@skaegi
Copy link
Contributor

skaegi commented Apr 9, 2020

/reopen
/assign
There is the serviceAccount workaround but I think this is still reasonable to add based on how some teams would like to use Tekton. If not me I'll find someone to work on adding support.

@tekton-robot
Copy link
Collaborator

@skaegi: Reopened this issue.

In response to this:

/reopen
/assign
There is the serviceAccount workaround but I think this is still reasonable to add based on how some teams would like to use Tekton. If not me I'll find someone to work on adding support.

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.

@animeshsingh
Copy link

@skaegi @afrittoli please take a look

@NikeNano
Copy link

NikeNano commented May 5, 2020

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 ?

@Tomcli
Copy link
Contributor

Tomcli commented Jun 9, 2020

Thanks @NikeNano for adding this feature. I think this issue can be closed.

@vdemeester
Copy link
Member

/close

@tekton-robot
Copy link
Collaborator

@vdemeester: Closing this issue.

In response to this:

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Indicates an issue or PR that deals with the API. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

8 participants