Skip to content

Release v1.28.1+k3s1 isn't marked as latest #8338

Answered by brandond
aofei asked this question in Q&A
Discussion options

You must be logged in to vote

Nope. We don't want it marked as latest, due to the upstream init container issue called out in the release notes. We'll mark v1.28.2 latest, after it is released next week.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by aofei
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #8337 on September 11, 2023 09:48.