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
You can bypass the automatic network verification if you want to deploy
9
+
You can bypass the automatic network verification if you want to deploy
10
10
ifdef::openshift-dedicated[]
11
-
an {product-title}
11
+
an {product-title}
12
12
endif::openshift-dedicated[]
13
13
ifdef::openshift-rosa[]
14
-
a {product-title} (ROSA)
14
+
a {product-title} (ROSA)
15
15
endif::openshift-rosa[]
16
16
cluster with known network configuration issues into an existing Virtual Private Cloud (VPC).
17
17
@@ -23,20 +23,21 @@ ifdef::openshift-rosa[]
23
23
endif::openshift-rosa[]
24
24
When you install a cluster into an existing VPC by using {cluster-manager-first}, you can bypass the automatic verification by selecting *Bypass network verification* on the *Virtual Private Cloud (VPC) subnet settings* page.
25
25
26
-
ifdef::openshift-rosa[]
27
-
.Bypassing automatic network verification by using the ROSA CLI (`rosa`)
26
+
//Commented out due to updates made in OSDOCS-7033
27
+
//ifdef::openshift-rosa[]
28
+
//.Bypassing automatic network verification by using the ROSA CLI (`rosa`)
28
29
29
-
When you install a cluster into an existing VPC by using the `rosa create cluster` command, you can bypass the automatic verification by including the `--bypass-network-verify --force` arguments. The following example bypasses the network verification before creating a cluster:
30
+
//When you install a cluster into an existing VPC by using the `rosa create cluster` command, you can bypass the automatic verification by including the `--bypass-network-verify --force` arguments. The following example bypasses the network verification before creating a cluster:
Alternatively, you can specify the `--interactive` argument and select the option in the interactive prompts to bypass the network verification checks.
41
-
====
42
-
endif::openshift-rosa[]
39
+
//[NOTE]
40
+
//====
41
+
//Alternatively, you can specify the `--interactive` argument and select the option in the interactive prompts to bypass the network verification checks.
Copy file name to clipboardExpand all lines: modules/running-network-verification-manually-cli.adoc
+41-19Lines changed: 41 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@
9
9
10
10
You can manually run the network verification checks for an existing {product-title} (ROSA) cluster by using the ROSA CLI (`rosa`).
11
11
12
-
When you run the network verification, you can specify a set of VPC subnet IDs or a cluster name. If you are using a proxy service, you can specify a proxy URL.
12
+
When you run the network verification, you can specify a set of VPC subnet IDs or a cluster name.
13
13
14
14
.Prerequisites
15
15
@@ -19,56 +19,78 @@ When you run the network verification, you can specify a set of VPC subnet IDs o
19
19
20
20
.Procedure
21
21
22
-
* Verify the network configuration by using one of the following methods:
22
+
* Verify the network configuration by using one of the following methods:
23
23
** Verify the network configuration by specifying the cluster name. The subnet IDs are automatically detected:
24
24
+
25
25
[source,terminal]
26
26
----
27
-
$ rosa verify network -c <cluster_name> <1>
27
+
$ rosa verify network --cluster <cluster_name> <1>
28
28
----
29
29
<1> Replace `<cluster_name>` with the name of your cluster.
30
30
+
31
31
.Example output
32
32
[source,terminal]
33
33
----
34
-
I: ✓ Network verification successful
34
+
I: Verifying the following subnet IDs are configured correctly: [subnet-03146b9b52b6024cb subnet-03146b9b52b2034cc]
35
+
I: subnet-03146b9b52b6024cb: pending
36
+
I: subnet-03146b9b52b2034cc: passed
37
+
I: Run the following command to wait for verification to all subnets to complete:
38
+
rosa verify network --watch --status-only --region us-east-1 --subnet-ids subnet-03146b9b52b6024cb,subnet-03146b9b52b2034cc
39
+
----
40
+
*** Ensure that verification to all subnets has been completed:
<1> The `watch` flag causes the command to complete after all the subnets under test are in a failed or passed state.
50
+
<2> The `status-only` flag does not trigger a run of network verification but returns the current state, for example, `subnet-123 (verification still in-progress)`. By default, without this option, a call to this command always triggers a verification of the specified subnets.
51
+
<3> Use a specific AWS region that overrides the _AWS_REGION_ environment variable.
52
+
<4> Enter a list of subnet IDs separated by commas to verify. If any of the subnets do not exist, the error message `Network verification for subnet 'subnet-<subnet_number> not found` displays and no subnets are checked.
53
+
+
54
+
.Example output
55
+
[source,terminal]
56
+
----
57
+
I: Checking the status of the following subnet IDs: [subnet-03146b9b52b6024cb subnet-03146b9b52b2034cc]
58
+
I: subnet-03146b9b52b6024cb: passed
59
+
I: subnet-03146b9b52b2034cc: passed
35
60
----
36
61
+
37
62
[TIP]
38
63
====
39
64
To output the full list of verification tests, you can include the `--debug` argument when you run the `rosa verify network` command.
40
65
====
41
66
+
42
-
** Verify the network configuration by specifying the VPC subnets IDs:
67
+
** Verify the network configuration by specifying the VPC subnets IDs. Replace `<region_name>` with your AWS region and `<AWS_account_ID>` with your AWS account ID:
43
68
+
44
69
[source,terminal]
45
70
----
46
-
$ rosa verify network --subnet-ids subnet-03146b9b52b6024cb,subnet-03146b9b52b2034cc
71
+
$ rosa verify network --subnet-ids 03146b9b52b6024cb,subnet-03146b9b52b2034cc --region <region_name> --role-arn arn:aws:iam::<AWS_account_ID>:role/my-Installer-Role
0 commit comments