On July 26, 2023, the KubeSphere open source community excitedly announced to everyone that KubeSphere 3.4.0 is officially released!
Let us briefly review the main changes of the previous three major versions:
- KubeSphere 3.1.0 adds functions such as "edge computing" and "metering and billing" to extend Kubernetes from the cloud to the edge;
- KubeSphere 3.2.0 has added support for "GPU resource scheduling management" and GPU usage monitoring, which further enhances the experience in cloud-native AI scenarios;
- KubeSphere 3.3.0 adds a GitOps-based continuous deployment solution, which further optimizes the DevOps experience.
Today, KubeSphere 3.4.0 has been officially launched. This version brings new features and enhancements worthy of everyone's attention: expand the scope of support for Kubernetes, and the latest stability supports 1.26; reconstruct the alarm policy architecture and decouple it into alarm rules and rules group; increase the display weight of the cluster alias, reduce the management problems caused by the unmodifiable original cluster name; upgrade the KubeEdge component to v1.13, etc. At the same time, a number of repairs, optimizations and enhancements have been made to further improve the interaction design and improve the user experience in an all-round way.
Here, I am very grateful to all the participants and contributors of this version. At the end of the article, we will list the IDs of all contributors to express our gratitude!
major update
Optimize alarm configuration
KubeSphere 3.4.0 optimizes the alarm configuration and adds different ranges of alarm rule groups:
- The original single alarm policy is split into multiple rule groups, and the minimum execution unit of the alarm is configured through the rule group
- Support editing, disabling and resetting of built-in alarm rules
Increase the display weight of cluster aliases
Operation and maintenance personnel often need to define cluster names to manage clusters in different locations and geographical locations. In the previous version, the cluster only supports name definition when it is managed, which undoubtedly brings a lot of operational troubles to the operation and maintenance personnel.
In response to this problem, KubeSphere 3.4.0 has made corresponding changes to increase the weight of cluster alias display, realize cluster alias and name management at the same level, and help users complete all original operations on names through aliases, or through Alias modification enables flexible management of clusters.
Support setting the default mirror warehouse
In a private environment, the default dockerhub needs to be replaced with a private warehouse. In previous versions, it was not supported to specify the default warehouse, and only manual selection was possible. If there are multiple private warehouses, users tend to ignore them during operation and cause operational errors.
In KubeSphere 3.4.0, we support setting the default mirror repository, making user operations easier and more convenient.
Other optimizations and enhancements
In addition to the above main functions, KubeSphere 3.4.0 has many optimizations and enhancements:
- Support Kubernetes v1.26
- Upgrade KubeEdge components to v1.13
- Use OpenSearch v2.6.0 as internal log storage by default, no longer use Elasticsearch as internal log storage by default
- Support pod grace period configuration
- Upgrade Notification Manager version to v2.3.0
- Upgrade go version to v1.19
- Optimize user experience for multi-branch pipelines
- Fix helm repo pagination query error
- Fix gateway upgrade verification error
- Fix cluster gateway log and resource status display exception
For more update details, please check the release note .
Install and upgrade
KubeSphere has synchronized and backed up all images of v3.4.0 in the domestic image warehouse, and the installation experience of domestic users downloading images will be more friendly.
If you find any bugs after installation and use, you are welcome to submit an Issue .
thank you
Below are the contributors who contributed to this release, thanks to everyone!
- leoendless
- yazhouio
- Bettygogo2021
- weili520
- harrisonliu5
- junotx
- smartcat999
- wansir
- imjoey
- sekfung
- renyunkang
- Fritzmomoto
- snowgo
- hongzhouzi
- chuan-you
- zhou1203
- iawia002
- sologgfun
- testwill
- LQBing
- littlejiancc
- wenchajun
The community will issue certificates to new contributors in the community bi-weekly report , and will also update them in time on the forum certificate wall . If there is anything missing, please contact us for reissue.
This article is published by OpenWrite, a multi-post platform for blogging !