Skip to content

add label when import managedhub #3

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

Closed
wants to merge 1 commit into from
Closed

add label when import managedhub #3

Show file tree
Hide file tree
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
15 changes: 10 additions & 5 deletions global_hub/global_hub_import_hub_default.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,19 @@
[#global-hub-importing-managed-hub-in-default-mode]
= Importing a managed hub cluster in the default mode

To import an existing hub cluster as a managed hub cluster, complete the following steps:
[#global-hub-importing-prereq]
== Prerequisites

- Disable the cluster self-management in the existing {acm} hub cluster by setting the `disableHubSelfManagement` setting to `true` in the `multiclusterhub` custom resource.

. Disable the cluster self-management in the existing {acm} hub cluster by setting the `disableHubSelfManagement` setting to `true` in the `multiclusterhub` custom resource. This setting disables the automatic importing of the hub cluster as a managed cluster.
To import an existing hub cluster as a managed hub cluster, complete the following steps:

. Import the managed hub cluster by completing the steps in link:../clusters/cluster_lifecycle/import_intro.adoc#import-intro[Cluster import introduction].
. Import the managed hub cluster by completing the steps in link:../clusters/cluster_lifecycle/import_intro.adoc#import-intro[Cluster import introduction]. You must set the label `global-hub.open-cluster-management.io/deploy-mode=default` to the managedcluster when you import it.

. After the managed hub cluster is imported, check the {global-hub} agent status to ensure that the agent is running in the managed hub cluster by running the following command:
+
----
oc get managedclusteraddon multicluster-global-hub-controller -n $<managed_hub_cluster_name>
----
oc get managedclusteraddon multicluster-global-hub-controller -n <managed_hub_cluster_name>
----

Note: If you try to upgrade the Globalhub from 1.4.x, you must manually add the label `global-hub.open-cluster-management.io/deploy-mode=default` to all managed hub clusters.
19 changes: 8 additions & 11 deletions global_hub/global_hub_import_hub_hosted.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,8 @@ To enable `local-cluster` on your managed hub cluster, you must import it in the
[#global-hub-importing-hosted-mode]
== Importing a hub cluster in the hosted mode

To import an existing managed hub cluster that has `local-cluster` enabled, you must use the hosted mode. In the hosted mode, you only get support for imported managed hub clusters that use a `kubeconfig` file. {acm} uses this `kubeconfig` file to generate the `auto-import-secret`, which connects to your managed hub cluster.

*Notes:*
To import an existing managed hub cluster in hosted mode, you only get support for imported managed hub clusters that use a `kubeconfig` file. {acm} uses this `kubeconfig` file to generate the `auto-import-secret`, which connects to your managed hub cluster.

- Make sure this `kubeconfig` file is always usable. If it expires, regenerate the `auto-import-secret` in the managed hub cluster namespace with the following command:
+
Expand All @@ -26,12 +25,10 @@ oc create secret generic auto-import-secret --from-file=kubeconfig=./managedClus

Complete the following steps:

. Set the annotation `global-hub.open-cluster-management.io/import-cluster-in-hosted: "true"` to `globalhub cr`.
. Import your managed hub cluster.

With this annotation, {global-hub} does the following actions:

- Imports all the new managed hub clusters in hosted mode.
- Disables the following `addons` in the new managed hub clusters namespaces: `applicationManager`, `certPolicyController`, and `policyController`.
- Changes the following managed hub clusters `addons` that are related to the new namespace: `work-manager`,`cluster-proxy`, and `managed-serviceaccount`.
- Changes these namespaces to `open-cluster-management-global-hub-agent-addon`.
. Import your managed hub cluster By setting label `global-hub.open-cluster-management.io/deploy-mode=hosted` to managedcluster
With this label, {global-hub} does the following actions:
- Imports the new managed hub cluster in hosted mode.
- Install Globalhub Agent in the new managed hub cluster using hosted mode.
- Disables the following `addons` in the new managed hub clusters namespaces: `applicationManager`, `certPolicyController`, and `policyController`.
- Changes the following managed hub clusters `addons` that are related to the new namespace: `work-manager`,`cluster-proxy`, and `managed-serviceaccount`.
- Changes these namespaces to `open-cluster-management-global-hub-agent-addon`.
Loading