You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/runtime/managed-cluster.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,9 +32,8 @@ Optionally, to first generate the YAML manifests, and then manually apply them,
32
32
List View: Select the**Managed Clusters** tab, and then select**+ Add Cluster**.
33
33
1. In the Add Managed Cluster panel, copy and run the command:
34
34
35
-
`cf cluster add<runtime-name>[--dry-run]`
35
+
`cf cluster add [--dry-run]`
36
36
where:
37
-
`<runtime-name>` is the runtime to which to register the cluster. The name of the selected runtime is automatically added.
38
37
`--dry-run` is optional, and required if you want to generate a list of YAML manifests that you can redirect and apply manually with`kubectl`.
39
38
40
39
{% include
@@ -49,7 +48,6 @@ Optionally, to first generate the YAML manifests, and then manually apply them,
49
48
50
49
{:start="5"}
51
50
1. When prompted, select the kube context from the list of available clusters as defined in`kubeconfig`. The kube context must have the credentials to communicate with the managed cluster.
52
-
53
51
1. If you used`dry-run`, apply the generated manifests to the same target cluster on which you ran the command.
54
52
Here is an example of the YAML manifest generated with the`--dry-run` flag. Note that there are placeholders in the example, which are replaced with the actual values with`--dry-run`.