1.4. Glossary of terms


Red Hat Advanced Cluster Management for Kubernetes consists of several multicluster components that are defined in the following sections. Additionally, some common Kubernetes terms are used within the product. Terms are listed alphabetically.

1.4.1. Relevant standardized glossaries

1.4.2.1. Application lifecycle

The processes that are used to manage application resources on your managed clusters. A multicluster application uses a Kubernetes specification, but with additional automation of the deployment and lifecycle management of resources to individual clusters.

1.4.2.2. Channel

A custom resource definition that points to repositories where Kubernetes resources are stored, such as a Git repository, Helm chart repository, object store, or hub cluster namespace. Channels support multiple subscriptions from multiple targets.

1.4.2.3. Cluster lifecycle

Defines the process of creating, importing, and managing clusters across public and private clouds.

1.4.2.4. Console

The graphical user interface for Red Hat Advanced Cluster Management.

1.4.2.5. Deployable

A resource that retrieves the output of a build, packages the output with configuration properties, and installs the package in a predefined location so that it can be tested or run.

1.4.2.6. Governance and risk

The Red Hat Advanced Cluster Management processes used to manage security and compliance.

1.4.2.7. Hub cluster

The central controller that runs in a Red Hat Advanced Cluster Management for Kubernetes cluster. From the hub cluster, you can access the console and components found on that console, as well as APIs.

1.4.2.8. Managed cluster

Created and imported clusters are managed by the klusterlet agent and its add-ons, which initiates a connection to the Red Hat Advanced Cluster Management for Kubernetes hub cluster.

1.4.2.9. Klusterlet

The agent that contains two controllers on the managed cluster that initiates a connection to the Red Hat Advanced Cluster Management for Kubernetes hub cluster.

1.4.2.10. Klusterlet add-on

Specialized controller on the Klusterlet that provides additional management capability.

1.4.2.11. Placement policy

A policy that defines where the application components should be deployed and how many replicas there should be.

1.4.2.12. Placement rule

A rule that defines the target clusters where subscriptions are delivered. For instance, verify the cluster name, resource annotations, or resource label(s).

1.4.2.13. Subscriptions

Identify Kubernetes resources within channels (resource repositories). The subscription places the Kubernetes resources in the same namespace, where it is created on the subscribed target clusters.

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat