Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit2c1c45a

Browse files
authored
Update managed-cluster.md (#162)
Removed runtime name from command
1 parentffc1bdd commit2c1c45a

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

‎_docs/runtime/managed-cluster.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,8 @@ Optionally, to first generate the YAML manifests, and then manually apply them,
3232
List View: Select the**Managed Clusters** tab, and then select**+ Add Cluster**.
3333
1. In the Add Managed Cluster panel, copy and run the command:
3434

35-
`cf cluster add<runtime-name>[--dry-run]`
35+
`cf cluster add [--dry-run]`
3636
where:
37-
`<runtime-name>` is the runtime to which to register the cluster. The name of the selected runtime is automatically added.
3837
`--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`.
3938

4039
{% include
@@ -49,7 +48,6 @@ Optionally, to first generate the YAML manifests, and then manually apply them,
4948

5049
{:start="5"}
5150
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-
5351
1. If you used`dry-run`, apply the generated manifests to the same target cluster on which you ran the command.
5452
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`.
5553

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp