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/vendor/testing-network-policy.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
This topic describes how to change the network policy of a virtual machine (VM) or a VM-based cluster with Replicated Compatibility Matrix, and how to collect and analyze network events to understand your application's behavior in air-gapped environments.
4
4
5
-
## Overview
5
+
## Set Network Policy to `airgap`
6
6
7
7
VMs and [VM-based clusters](/vendor/testing-supported-clusters#vm-clusters) created with Compatibility Matrix can use one of the following network policies:
8
8
@@ -13,14 +13,7 @@ VMs and [VM-based clusters](/vendor/testing-supported-clusters#vm-clusters) crea
13
13
14
14
By default, all VMs and clusters are created with an `open` network policy. You can change the network policy to `airgap` to simulate an air-gapped environment with no outbound internet access. This `airgap` network policy is particularly useful for previewing how your application will perform in air-gapped end customer environments.
15
15
16
-
Compatibility Matrix also supports collecting network reports. Viewing a report of network events can help you understand your application's behavior in air-gapped environments, with details on outbound network requests.
17
-
18
-
Network policy enforcement is separate from network reporting. For greater flexibility in testing, the report captures all network activity whether the policy is set to `open` or `airgap`.
19
-
20
-
21
-
## Set Network Policy to `airgap`
22
-
23
-
To simulate an air-gapped environment that prevents outbound network requests, you can change the policy for a network from `open` to `airgap`. Network policies are configured at the network level and apply to all VMs and clusters within the network.
16
+
Network policies are configured at the network level and apply to all VMs and VM-based clusters within the network.
24
17
25
18
### For VM-Based Clusters
26
19
@@ -118,9 +111,14 @@ To set the network policy of a VM:
118
111
```
119
112
120
113
1. (Optional) To verify that there is no outbound connectivity from the VM, enable network reporting and view network events. See [Collect and View Network Reports](#collect-and-view-network-reports).
114
+
121
115
## Collect and View Network Reports
122
116
123
-
Compatibility Matrix network reporting helps you understand your application's network activity. Even when the network policy is set to `airgap` and network egress is blocked, all connection attempts and DNS queries are still captured in the report. This helps you identify unexpected network calls before deploying to an air-gapped environment.
117
+
Compatibility Matrix network reporting helps you understand your application's network activity. To provide flexibility in testing, you can enable network reporting to capture all network activity, whether the network policy is set to `open` or `airgap`. Even when the network policy is set to `airgap` and network egress is blocked, all connection attempts and DNS queries are still captured in the report. This helps you identify unexpected network calls before deploying to an air-gapped environment.
118
+
119
+
Network reporting is not enabled by default. For information about how to collect and view reports through the Vendor Portal or the Replicated CLI, see the sections below.
120
+
121
+
The following table describes the contents of the supported network report types:
124
122
125
123
| Report Type | Contents |
126
124
|---|---|
@@ -129,7 +127,7 @@ Compatibility Matrix network reporting helps you understand your application's n
129
127
130
128
### Vendor Portal
131
129
132
-
In Vendor Portal, you can set network policy, and collect network reports:
130
+
To setthe network policy and collect and view reportsin the Vendor Portal:
133
131
134
132
1. Go to **Compatibility Matrix**>**Network Policy**.
0 commit comments