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

Commitffc1bdd

Browse files
authored
Update add cluster (#161)
* Update add clusterRemoved context from command and updated screenshot* Update image for add cluster* Update managed-cluster.mdCommented out note on results of removing cluster
1 parentf59bb06 commitffc1bdd

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

‎_docs/runtime/managed-cluster.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -30,13 +30,11 @@ Optionally, to first generate the YAML manifests, and then manually apply them,
3030
1. From either the**Topology** or**List** views, select the runtime to which to add the cluster.
3131
1. Topology View: Select {::nomarkdown}<imgsrc="../../../images/icons/add-cluster.png"display=inline-block/>{:/}.
3232
List View: Select the**Managed Clusters** tab, and then select**+ Add Cluster**.
33-
1. In the Add Managed Cluster panel:
34-
***Cluster Name**: Enter the context name for your cluster (as it appears in your kubeconfig file).
35-
* Define the parameters and then run the command:
36-
`cf cluster add <runtime-name> --context <context_name> [--dry-run]`
33+
1. In the Add Managed Cluster panel, copy and run the command:
34+
35+
`cf cluster add <runtime-name> [--dry-run]`
3736
where:
3837
`<runtime-name>` is the runtime to which to register the cluster. The name of the selected runtime is automatically added.
39-
`<context_name>` is the kube context with the credentials to communicate with the managed cluster. If not supplied, the CLI displays the list of available clusters as defined in`kubeconfig`.
4038
`--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`.
4139

4240
{% include
@@ -46,10 +44,12 @@ Optionally, to first generate the YAML manifests, and then manually apply them,
4644
url="/images/runtime/managed-cluster-add-panel.png"
4745
alt="Add Managed Cluster panel"
4846
caption="Add Managed Cluster panel"
49-
max-width="30%"
47+
max-width="40%"
5048
%}
5149

5250
{:start="5"}
51+
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+
5353
1. If you used`dry-run`, apply the generated manifests to the same target cluster on which you ran the command.
5454
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`.
5555

@@ -222,7 +222,7 @@ Use the Topology or List runtime views to work with managed clusters. For inform
222222

223223
**Remove cluster**
224224
Remove a cluster registered with a runtime from the runtime's list of managed clusters.
225-
>Removing a managed cluster from a runtime also removes all the applications deployed to the cluster, and removes their data from the Applications dashboard.
225+
<!-->>Removing a managed cluster from a runtime also removes all the applications deployed to the cluster, and removes their data from the Applications dashboard.-->
226226

227227
**How to**
228228
1. In the Codefresh UI, go to the [Runtimes](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"} page.
27.5 KB
Loading

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp