From ba8953cadc9e72b9da12f836312c011aaf6e8cea Mon Sep 17 00:00:00 2001 From: Abhijith Ravindra <137736216+abhijith-darshan@users.noreply.github.com> Date: Thu, 22 Aug 2024 07:21:52 +0200 Subject: [PATCH] (fix): typo in docs (#470) fixes grammatical mistake in onboarding docs --- docs/user-guides/cluster/onboarding.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guides/cluster/onboarding.md b/docs/user-guides/cluster/onboarding.md index 379f07797..c8ff44e6f 100644 --- a/docs/user-guides/cluster/onboarding.md +++ b/docs/user-guides/cluster/onboarding.md @@ -16,7 +16,7 @@ NOTE: The UI is currently in development. For now this guide describes the onboa ### Preparation -Download the latest `greenhousectl` binary for from [here](https://github.com/cloudoperators/greenhouse/releases). +Download the latest `greenhousectl` binary from [here](https://github.com/cloudoperators/greenhouse/releases). The command line tool requires access to both the Greenhouse **and** your Kubernetes cluster. Hence, have the `kubeconfig` files for both clusters at hand. The `kubeconfig` file for the Greenhouse Kubernetes cluster can be downloaded via the Greenhouse dashboard: _Organization_ > _Clusters_ > _Access greenhouse cluster_. @@ -85,4 +85,4 @@ When the `status.kubernetesVersion` field shows the correct version of the Kuber In the remote cluster, a new namespace is created and contains some resources managed by Greenhouse. The namespace has the same name as your organization in Greenhouse. -If the bootstrapping failed, you can delete the Kubernetes cluster from Greenhouse with `kubectl --namespace= delete cluster ` and run the bootstrap command again. \ No newline at end of file +If the bootstrapping failed, you can delete the Kubernetes cluster from Greenhouse with `kubectl --namespace= delete cluster ` and run the bootstrap command again.