For every Kubernetes cluster that wants to be managed, we call it child cluster. The cluster where child clusters are registerring to, we call it parent cluster.
clusternet-agent runs in child cluster, while
clusternet-hub runs in parent cluster.
ClusterRegistrationRequestis an object that
clusternet-agentcreates in parent cluster for child cluster registration.
ManagedClusteris an object that
clusternet-hubcreates in parent cluster after approving
HelmChartis an object contains a helm chart configuration.
Subscriptiondefines the resources (we call them as a group of
Feeds) that subscribers want to install into clusters. Various
SchedulingStrategyare supported, such as
DynamicDividing. For every matched cluster, a corresponding
Baseobject will be created in its dedicated namespace.
Clusternetprovides a two-stage priority based override strategy.
Globalizationwill define the overrides with priority, where lower numbers are considered lower priority.
Localizationis namespace-scoped resource, while
Globalizationis cluster-scoped. Refer to tutorial on how to set overrides in Clusternet.
Baseobjects will be rendered to
Descriptionis the final resources to be deployed into target child clusters.
FeedInventoryobjects are used to track and record the scheduling requirements (such as replicas, node selectors, tolerations, affinity rules, resource requirements, etc.) for each feed in the
Subscriptionobject of the same name. This
FeedInventoryobject is only applicable when
SchedulingStrategyis set to
DynamicDividing. For other scheduling strategies,
FeedInventorymakes no sense.
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.