-
Notifications
You must be signed in to change notification settings - Fork 110
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
Keep required Kubernetes version synced in prow/config.yaml #1283
Comments
I think, ideally, prow itself shouldn't have that information, and everything would "come" from each component. |
Thanks @vdemeester , that makes perfect sense. So that being said, we might need to put this into a checklist whenever we are updating the required version? |
@JeromeJu yes, and this is also ideally, and we might still need to handle this in plumbing for some time, so yes we definitely need some up-to-date checklist here and on each component repositories on what to do when we update the min k8s version we support. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: 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. |
Feature request
The required Kubernetes version in prow/config for example https://github.com/tektoncd/plumbing/blob/main/prow/config.yaml#L838 is hardcoded and this should be synced or have a way to be updated once Tektoncd have updated the required version.
Use case
#1279 (comment)
The text was updated successfully, but these errors were encountered: