Skip to content

Commit

Permalink
(fix): typo in docs (#470)
Browse files Browse the repository at this point in the history
fixes grammatical mistake in onboarding docs
  • Loading branch information
abhijith-darshan authored Aug 22, 2024
1 parent c179ed7 commit ba8953c
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/user-guides/cluster/onboarding.md
Original file line number Diff line number Diff line change
Expand Up @@ -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_.
Expand Down Expand Up @@ -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=<greenhouse-organization-name> delete cluster <name>` and run the bootstrap command again.
If the bootstrapping failed, you can delete the Kubernetes cluster from Greenhouse with `kubectl --namespace=<greenhouse-organization-name> delete cluster <name>` and run the bootstrap command again.

0 comments on commit ba8953c

Please sign in to comment.