Keep required Kubernetes version synced in prow/config.yaml

[JeromeJu]

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)

[vdemeester]

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)

I think, ideally, prow itself shouldn't have that information, and everything would "come" from each component.

[JeromeJu]

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?

[vdemeester]

@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.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

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.