Skip to content

update install globalhub in existing acmhub #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 2.14_stage
Choose a base branch
from
Open

update install globalhub in existing acmhub #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
21 changes: 12 additions & 9 deletions global_hub/global_hub_install_acm.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,20 @@
[#global-hub-install-acm]
= Installing {global-hub} on an existing {acm-short} hub cluster (Technology Preview)
= Installing {global-hub} on an existing {acm-short} hub cluster

When you create the `MultiClusterGlobalHub` custom resource (CR), you must set the `installAgentOnLocal` field to `true`. The `installAgentOnLocal` field determines if you can deploy {global-hub} on an existing {acm-short} hub cluster.
You can install {global-hub} in an existing {acm-short} hub cluster, and enable the {global-hub} agent in the {acm-short}.
with this:
- All the clusters, policies, and events in this {acm-short} will be sent to Kafka and then stored in the globalhub database.
- Since the events will be sent to Kafka, other components can easily consume the events in Kafka, e.g., integration with [Red Hat Advanced Cluster Security](https://github.com/stolostron/stolostron/tree/main/dev-preview#global-hub-integration-with-red-hat-advanced-cluster-security) or EDA integration.
- Since the data will be stored in the globalhub database, you can view cluster and policy information in Grafana dashboards.

Before you create `MultiClusterGlobalHub` custom resource (CR), you must complete the following procedures:


[#global-hub-install-operator-prerequisites]
== Prerequisites
* xref:../global_hub/global_hub_install_connected.adoc#global-hub-install-connected[Installing Multicluster Global Hub in a connected environment]
* xref:../global_hub/global_hub_install_disconnected.adoc#global-hub-install-disconnected[Installing Multicluster Global Hub in a disconnected environment]

To install {global-hub} on an existing {acm-short} hub cluster, complete the following steps:

. Install a {global-hub} operator from the `OperatorHub`.
. In the {ocp} console, create a `MultiClusterGlobalHub` CR.
. Apply the `MultiClusterGlobalHub` CR to your {global-hub} operator.
. Set the `installAgentOnLocal` field to `true` by applying the following YAML sample:
To install {global-hub} on an existing {acm-short} hub cluster, you must set the `installAgentOnLocal` field to `true` by applying the following YAML sample:

+
[source,yaml]
Expand All @@ -38,3 +39,5 @@ spec:

The {global-hub} agent is now automatically installed on an existing {acm-short} hub cluster.

Notes:
If you enabled MultiCluster Observability in the {acm-short}, after the {globalhub} installed, any new update for `MultiClusterObservability` will not take effect.
Loading