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

Why mimic k8s version number? #11

Closed
errordeveloper opened this issue Dec 21, 2018 · 1 comment
Closed

Why mimic k8s version number? #11

errordeveloper opened this issue Dec 21, 2018 · 1 comment

Comments

@errordeveloper
Copy link
Contributor

It seems like the actual version is very very different anyway.
@errordeveloper errordeveloper changed the title Why present similar version number? Why mimic k8s version number? Dec 21, 2018
@ibuildthecloud
Copy link
Contributor

I'll be releasing k3s with it's own versioning scheme now that I've separated the k3s and k8s repos. The patched k8s repo will still have a version based off of upstream like v1.13.2-k3s2.

@billimek billimek mentioned this issue Oct 23, 2019
Closed
@pentago pentago mentioned this issue Dec 3, 2020
Closed
@chinasoftgit chinasoftgit mentioned this issue May 6, 2022
Closed
@mbrandeburg mbrandeburg mentioned this issue Jan 18, 2024
Closed
@sharrurashmi sharrurashmi mentioned this issue Jun 27, 2024
Closed
@UriZafrir UriZafrir mentioned this issue Oct 21, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@errordeveloper @ibuildthecloud