Skip to content
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

Added a note on non-scripted creation of clusters #418

Merged
merged 1 commit into from
Oct 28, 2023
Merged

Added a note on non-scripted creation of clusters #418

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
2 changes: 2 additions & 0 deletions docs/content/en/docs/fleet-manager/manage-attachedcluster.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,8 @@ As the AttachedCluster object is controlled by the cluster-operator, you need to

From these clusters created by `hack/local-dev-setup.sh`, we'll select kurator-member1 and kurator-member2 to be attached to the Kurator Fleet.

If you didn't create the corresponding cluster using our script, you need to change the kubeconfig file in which you created the cluster yourself. You can find your kubeconfig in `/root/.kube/config`, then Change the server field to the IP address of your cluster control plane node(you can get it from `kubectl get nodes -owide`) and the port number to 6443.

Next, we'll create secrets containing the kubeconfig information of these clusters. Make sure to replace the paths like `/root/.kube/kurator-member1.config` with the actual kubeconfig file paths on your system.

```console
Expand Down
Loading