-
Notifications
You must be signed in to change notification settings - Fork 20
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
TT-9846 allow setting imagePullSecrets #97
TT-9846 allow setting imagePullSecrets #97
Conversation
for charts that allow setting image.repository
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.
@rakkhin thank you for this great contribution! Can you also update tyk-bootstrap component as well, just to be consistent across all components? Please let me know if you have any questions.
@buraksekili I didn't want to touch bootstrap since images for resources defined there are hardcoded. But if it's OK with you I can bring those in line with other components. |
@rakkhin you are right. let's keep them as it is. thank you again for the contribution. I'll move this ticket to QA |
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.
thank you @rakkhin for your contribution! LGTM
allow setting
imagePullSecrets
for charts that allow settingimage.repository
Description
Some organizations deploying Tyk in their infrastructure may have policies in place that require use of docker proxy for all 3rd party images. Those proxies almost always will requires authentication, but Tyk helm charts doesn't have option to set
imagePullSecrets
for those that allow setting image repo, effectively blocking those organizations from using self-hosted Tyk deployments.Related Issue
Resolves #96
Motivation and Context
Setting
imagePullSecrets
is required for orgs that use internal docker proxies with authentication.Test Coverage For This Change
Screenshots (if appropriate)
Types of changes
Checklist
master
!master
branch (left side). Also, it would be best if you started your change off our latestmaster
.