This release brings in multiple fantastic features and improves the performance. This is a 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 #378
, #405, #411
and by @xrmzju in #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 #366
, #395
, #400
, #419). Default predictors run on every clusternet-agent
,
external predictors had been supported as well (by @yinsenyan
in #367 and @dixudx
in #418)
. Learn more
from this tutorial
.clusternet-scheduler
(by @Garrybest
in #383
, #399
, #388)node.clusternet.io/
from nodes in child clusters (@lmxia
in #396
, #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 #362
, #365 and @DanielXLee
in #421)kubectl clusternet
plugin having consistent user experience with kubectl
(
by @lmxia in #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 #364)Thanks to all contributors!
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.