Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions hosted_control_planes/index.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1]

[role="_additional-resources"]
.Additional resources

* link:https://kubernetes.io/docs/reference/using-api/#api-versioning[Kubernetes API versioning]
* link:https://amd64.ocp.releases.ci.openshift.org/[AMD64 release images]
* link:https://arm64.ocp.releases.ci.openshift.org/[ARM64 release images]
* link:https://multi.ocp.releases.ci.openshift.org/[Multi-arch release images]
Expand Down
7 changes: 5 additions & 2 deletions modules/hcp-acm-discover.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,9 @@

:_mod-docs-content-type: CONCEPT
[id="hcp-acm-discover_{context}"]
= Discovering {mce-short} hosted clusters in {rh-rhacm}
= Hosted clusters in {rh-rhacm-title}

If you want to bring hosted clusters to a {rh-rhacm-first} hub cluster to manage them with {rh-rhacm} management components, see the instructions in the link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#discover-hosted-acm[{rh-rhacm-title} official documentation].
[role="_abstract"]
You can bring hosted clusters to a {rh-rhacm-title} hub cluster to manage them with {rh-rhacm-title} management components.

For more information, see "Discovering {mce-short} hosted clusters in {rh-rhacm-title}".
8 changes: 5 additions & 3 deletions modules/hosted-control-planes-concepts-personas.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,11 @@
// * hosted-control-planes/index.adoc


:_mod-docs-content-type: CONCEPT
:_mod-docs-content-type: REFERENCE
[id="hosted-control-planes-concepts-personas_{context}"]
= Glossary of common concepts and personas for {hcp}

[role="_abstract"]
When you use {hcp} for {product-title}, it is important to understand its key concepts and the personas that are involved.

[id="hosted-control-planes-concepts_{context}"]
Expand Down Expand Up @@ -38,9 +39,10 @@ cluster instance administrator:: Users who assume this role are the equivalent o

cluster instance user:: Users who assume this role are the equivalent of developers in standalone {product-title}. This user does not have a view into the software catalog or machines.

cluster service consumer:: Users who assume this role can request control planes and worker nodes, drive updates, or modify externalized configurations. Typically, this user does not manage or access cloud credentials or infrastructure encryption keys. The cluster service consumer persona can request hosted clusters and interact with node pools. Users who assume this role have RBAC to create, read, update, or delete hosted clusters and node pools within a logical boundary.
cluster service consumer:: Users who assume this role can request control planes and worker nodes, drive updates, or modify externalized configurations. Typically, this user does not manage or access cloud credentials or infrastructure encryption keys. The cluster service consumer persona can request hosted clusters and interact with node pools. Users who assume this role have role-based access control (RBAC) to create, read, update, or delete hosted clusters and node pools within a logical boundary.

cluster service provider:: Users who assume this role typically have the `cluster-admin` role on the management cluster and have RBAC to monitor and own the availability of the HyperShift Operator and the control planes for the tenant's hosted clusters. The cluster service provider persona is responsible for several activities, including the following examples:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 [error] RedHat.TermsErrors: Use 'hosted control planes' rather than 'HyperShift'. For more information, see RedHat.TermsErrors.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ignoring suggestion - this content is correctly referring to the HyperShift Operator


cluster service provider:: Users who assume this role typically have the `cluster-admin` role on the management cluster and have RBAC to monitor and own the availability of the HyperShift Operator as well as the control planes for the tenant's hosted clusters. The cluster service provider persona is responsible for several activities, including the following examples:
** Owning service-level objects for control plane availability, uptime, and stability
** Configuring the cloud account for the management cluster to host control planes
** Configuring the user-provisioned infrastructure, which includes the host awareness of available compute resources
7 changes: 5 additions & 2 deletions modules/hosted-control-planes-version-support.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,10 @@
[id="hosted-control-planes-version-support_{context}"]
= Versioning for {hcp}

The {hcp} feature includes the following components, which might require independent versioning and support levels:
[role="_abstract"]
The {hcp} feature includes several components that might require independent versioning and support levels.

Those components are as follows:

* Management cluster
* HyperShift Operator
Expand Down Expand Up @@ -62,7 +65,7 @@ You can use the `hcp` CLI to create hosted clusters. You can download the CLI fr

You can use the `hypershift.openshift.io` API resources, such as, `HostedCluster` and `NodePool`, to create and manage {product-title} clusters at scale. A `HostedCluster` resource contains the control plane and common data plane configuration. When you create a `HostedCluster` resource, you have a fully functional control plane with no attached nodes. A `NodePool` resource is a scalable set of worker nodes that is attached to a `HostedCluster` resource.

The API version policy generally aligns with the policy for link:https://kubernetes.io/docs/reference/using-api/#api-versioning[Kubernetes API versioning].
The API version policy generally aligns with the policy for Kubernetes API versioning.

Updates for {hcp} involve updating the hosted cluster and the node pools. For more information, see "Updates for {hcp}".

Expand Down