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.

Sign up for GitHub

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

Jump to bottom

Remove or fix the 'latest' feature #27

Closed
xunleii opened this issue Jul 18, 2020 · 0 comments · Fixed by #28
Closed

Remove or fix the 'latest' feature #27

xunleii opened this issue Jul 18, 2020 · 0 comments · Fixed by #28
Assignees
@xunleii

Comments

@xunleii
Copy link
Owner

xunleii commented Jul 18, 2020 •
edited
Loading

Because of this feature I break one of my cluster 🤦 ... because the k3s team has fixed a CVE (thanks for theirs works by the way), the last version available from the Github API was kube v1.16.13+k3s1 ... so my cluster jumps from v1.18 to v1.16 ...

⚠️ I DON'T RECOMMEND TO USE THIS FEATURE TODAY ... I need to find another way to do that or remove this feature
@xunleii xunleii added the bug label Jul 18, 2020
@xunleii xunleii changed the title Remove the 'latest' feature Remove or fix the 'latest' feature Jul 18, 2020
@xunleii xunleii self-assigned this Jul 18, 2020
@solidnerd solidnerd mentioned this issue Aug 2, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xunleii xunleii

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: use k3s update channels for latest releases instead of github solidnerd/terraform-module-k3s
1 participant
@xunleii