Skip to content

Commit

Permalink
minor changes
Browse files Browse the repository at this point in the history
  • Loading branch information
@Arvindthiru
Arvindthiru committed Aug 2, 2024
1 parent 16dffe7 commit 2a4a27c
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions docs/tutorials/JoinOnPremClustersToFleet.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,8 +16,8 @@ Follow these guides to setup your fleet and get access to your fleet hub cluster

Clone the [fleet repository](https://github.com/Azure/fleet) and navigate to the root directory of the repo.

Run the following script sets up the resources on the hub cluster and each on-prem cluster to allow the member agent
installed to be able to communicate with the hub cluster.
Run the following script which sets up the resources on the hub cluster and each on-prem cluster to allow
the member agent installed by the script on each on-prem cluster to communicate with the hub cluster.

The latest fleet image tag could be found here in [fleet releases](https://github.com/Azure/fleet/releases).

Expand All @@ -40,17 +40,16 @@ test-cluster-2 Unknown 2m30s 1 890m 3566856Ki

> **Note:** The `JOINED` column will be `Unknown` until the fleet networking member agent charts are installed on each on-prem cluster.
We can confirm that the member agent was installed correctly when we see `NODE-COUNT`, `AVAILABLE-CPU`, and `AVAILABLE-MEMORY` columns populated.
We can confirm that the member agent was installed correctly when we see `NODE-COUNT`, `AVAILABLE-CPU`, and `AVAILABLE-MEMORY` columns are populated.
The columns can take upto a minute to populate.

> **Note:** The script in the fleet-networking repo can only be used once the script in the fleet repo has been run.
> **Note:** The script in the fleet-networking repo should only be run once the script in the fleet repo has been run to ensure the member agents can communicate with the hub cluster.
Clone the [fleet-networking repository](https://github.com/Azure/fleet-networking) and navigate to the root directory of the repo.

Run the following script to join your on-prem clusters to the Fleet hub cluster by installing the fleet networking member agent controllers on each on-prem cluster.
Run the following script to install the fleet networking member agents on each on-prem cluster.

The latest fleet-networking image tag could be found here [fleet-networking releases](https://github.com/Azure/fleet-networking/releases).
Please ensure kubectl can access the kube-config of the hub cluster and all the on-prem clusters.

Ex: `./hack/Azure/joinMC.sh v0.1.0 v0.2.0 hub test-cluster-1 test-cluster-2`

Expand All @@ -67,6 +66,7 @@ test-cluster-1 True 3m17s 1 130m 2153732Ki
test-cluster-2 True 3m7s 1 690m 3304712Ki
```

The `JOINED` column will be `True` once both fleet networking member agent charts are installed on each on-prem cluster.
The column can take upto a minute to populate. The `JOINED` column indicates that the agent have all joined once.
The column is not meant for tracking each agent's health status.
The `JOINED` column will be `True` once both fleet networking member agent charts are installed on each on-prem cluster and the networking
member agents are able to communicate with fleet hub cluster.
The column can take upto a minute to populate. The `JOINED` column indicates that all three fleet member agents have all joined once.
The column is not meant for tracking each member agent's health status.

0 comments on commit 2a4a27c

Please sign in to comment.