Skip to content
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

[FEATURE] v0.13 Bump Tekton and Kubernetes dependencies #1505

Closed
1 task done
SaschaSchwarze0 opened this issue Feb 25, 2024 · 0 comments · Fixed by #1513
Closed
1 task done

[FEATURE] v0.13 Bump Tekton and Kubernetes dependencies #1505

SaschaSchwarze0 opened this issue Feb 25, 2024 · 0 comments · Fixed by #1513
Assignees
Labels
kind/dependency-change Categorizes issue or PR as related to changing dependencies

Comments

@SaschaSchwarze0
Copy link
Member

SaschaSchwarze0 commented Feb 25, 2024

Is there an existing feature request for this?

  • I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

For the v0.13 release, we should bump the Tekton and Kubernetes dependencies as usual.

Describe the solution that you would like.

Kubernetes 1.26 goes eol on 2/28.. We should therefore bump go.mod to the newest v0.27 version, and controller-runtime to the newest v0.15 version. In integration and e2e, we should test Kubernetes 1.27 and 1.29. Support statement should be adjusted to state that we support 1.27, 1.28, and 1.29.

The oldest still supported Tekton LTS release is v0.47, but it goes EOL on 3/17. I therefore suggest to bump go.mod to v0.50 (the next LTS release). In integration and e2e, I suggest to also test this version. We document v0.50 to be the minimum supported version.

Describe alternatives you have considered.

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/dependency-change Categorizes issue or PR as related to changing dependencies
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant