Hi Community,
Clusternet v0.11.0 is alive now!
This release brings
in multiple fantastic features and improves the performance.
This is a super big update of Clusternet
.
Running clusternet-hub
with high availability is possible now. And the performance of clusternet-scheduler
is improved as well. Dynamic replica scheduling is fully
supported. Applications with multiple replicas can be divided
and scheduled to multiple clusters based on cluster dynamic
capacity. Please check out this
tutorial. Moreover, the aggregated statuses of all
deployed resources can be shown by visiting the status of Subscription
.
Full Changelog: v0.10.0…v0.11.0
clusternet-hub
high availability (by @dixudx in https://github.com/clusternet/clusternet/pull/378,
https://github.com/clusternet/clusternet/pull/405,
https://github.com/clusternet/clusternet/pull/411
and by @xrmzju in https://github.com/clusternet/clusternet/pull/387)Subscription
.
For every feed/resource, you can check the detailed status
(field feedStatusDetails
)
per cluster and the summarized status (field feedStatusSummary
)
of all clusters in status.aggregatedStatuses
.Dynamic
for clusternet-scheduler
.
Applications with multiple replicas now can be divided and
scheduled to multiple clusters based on cluster dynamic
capacity. (by @Garrybest in https://github.com/clusternet/clusternet/pull/366,
https://github.com/clusternet/clusternet/pull/395,
https://github.com/clusternet/clusternet/pull/400,
https://github.com/clusternet/clusternet/pull/419).
Default predictors run on every clusternet-agent
,
external predictors had been supported as well (by @yinsenyan
in https://github.com/clusternet/clusternet/pull/367
and @dixudx in https://github.com/clusternet/clusternet/pull/418).
Learn more from this
tutorial.clusternet-scheduler
(by @Garrybest in https://github.com/clusternet/clusternet/pull/383,
https://github.com/clusternet/clusternet/pull/399,
https://github.com/clusternet/clusternet/pull/388)node.clusternet.io/
from nodes in child clusters (@lmxia in https://github.com/clusternet/clusternet/pull/396,
https://github.com/clusternet/clusternet/pull/413).
If all nodes of a child cluster have such common labels, then
these labels will be aggregated and updated to its
corresponding ManagedCluster
object.--use-metrics-server=true
on clusternet-agent
side (by @GeorgeGuo2018 in https://github.com/clusternet/clusternet/pull/362,
https://github.com/clusternet/clusternet/pull/365
and @DanielXLee in https://github.com/clusternet/clusternet/pull/421)kubectl clusternet
plugin having consistent user experience with kubectl
(by @lmxia in https://github.com/clusternet/clusternet/pull/384)ExecSync
API. This can cause containerd to consume all available memory
on the computer, denying service to other legitimate
workloads. Kubernetes and crictl can both be configured to use
containerd’s CRI implementation; ExecSync
may be used when running probes or when executing processes
via an “exec” facility. (by @dixudx in https://github.com/clusternet/clusternet/pull/364)Thanks to all contributors!