-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Chart: Remove isControllerTagValid
.
#11710
Conversation
✅ Deploy Preview for kubernetes-ingress-nginx canceled.
|
/triage accepted |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Gacko, ubergesundheit 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 |
/cherry-pick release-1.10 |
/cherry-pick release-1.11 |
@Gacko: #11710 failed to apply on top of branch "release-1.10":
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-sigs/prow repository. |
@Gacko: #11710 failed to apply on top of branch "release-1.11":
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-sigs/prow repository. |
What this PR does / why we need it:
This PR removes the
isControllerTagValid
template from the chart. According to its description, it should prevent users from installing old controller image versions, but this would require us to bump it with releases. Since nobody cared about it for a long time, I'd rather remove it and give users the possibility to define whatever image they want - even non-semver compliant ones.Keep in mind: With the current implementation you could easily use v0.28.0 without that template complaining. I don't think this is adding any value and only takes users the possibility of using custom tags.
Types of changes
Which issue/s this PR fixes
Fixes #11708.
Checklist: