-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Enable field imagePullSecrets for PodSpec #5917
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taragu: 0 warnings.
In response to this:
/lint
Part of #5866
Proposed Changes
- Enable users to specify imagePullSecrets in their service yaml
Release Note
Users will now be able to specify imagePullSecrets in their service yaml.
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.
25accfd
to
ad31936
Compare
The following is the coverage report on the affected files.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also take a stab at updating the specification with the new field? I owe some documentation on doing so, but bumping the lastUpdated, version (1.0.1), and adding the field with a description would be great.
https://github.com/knative/docs/blob/master/docs/serving/spec/knative-api-specification-1.0.md
@@ -98,7 +98,6 @@ | |||
- HostIPC | |||
- ShareProcessNamespace | |||
- SecurityContext | |||
- ImagePullSecrets |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add an integration test :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I agree. I'll create an issue and work on it as a separate PR. I'll also do these for updating the docs.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgerd, taragu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-serving-unit-tests:
|
/retest |
/lint
Part of #5866
Proposed Changes
Release Note