-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Plans for 2.1.1 and 3.0.0 #1368
Comments
Hey, i actuall just found out about this an it looks very promising. But i do have something for the 3.0.0 Release, currently Kubesphere only supports Kubernetes up to version 1.15, since the latest is 1.17 and my cluster already uses that i sadly can't try this out. Also i saw in the readme that Helm 3 is planned for 3.0.0 but its also not written down in here :). |
KubeSphere supports K8s 1.16 in the upcoming 2.1.1 release which is under intensive testing now. It might support K8s 1.17 too but we are short of hands to test it thoroughly. This note of plans is just general ideas about next steps, which means we only put big things here. The roadmap is the detailed tasks to do for next releases. BTW, Helm 3 will be supported in KubeSphere 3.0. |
when will 3.0.0 Release? |
the middle of May. |
does 2.1.1 support kubernetes 1.14.x? |
Actually it supports. Officially the roadmap of KubeSphere is to support the latest three versions of K8s for each release. That is why you see such document. |
Will you consider extending this version list? |
We tested on EKS. It does support 1.14. |
Okay! will you keep support 1.14 in the feature 3.0.0 version ? |
If most of cloud provider's k8s services upgrade to new version (> 1.14) about a month before we release 3.0, we may not support the older version. Otherwise, we will support it. |
Can 3.0.0 be released as expected in middle of May? looking forward 3.0.0! |
There are 2-4 weeks delay because of the COVID-19. |
We're close to the GA of 3.0.0, here are the main features and enhancements list for this major release:
|
Is there any improvments in auth management? |
sure, we do, which is upgrade and enhancement from backend perspective but not function perspective, including:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
We will release 2.1.0 in a few days. Next we will work on the first fixpack for 2.1.0 and the next major version 3.0.0.
Plan for 2.1.1
Plan for 3.0.0
In this major version, the big component will be multi-cluster management which brings huge design change for the current features such as monitoring, logging, app management etc. So most likely supporting multi-cluster management will be the only big one for 3.0.0. Besides that, we will add a few more functions such that
The text was updated successfully, but these errors were encountered: