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: articles/operator-nexus/howto-run-instance-readiness-testing.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Instance Readiness Testing (IRT) is a framework built to orchestrate real-world
18
18
1. A Linux environment (Ubuntu suggested) capable of calling Azure APIs
19
19
1. Knowledge of networks to use for the test
20
20
* Networks to use for the test are specified in a "network-blueprint.yml" file, see [Input Configuration](#input-configuration).
21
-
2. curl or wget to download IRT package
21
+
1. curl or wget to download IRT package
22
22
23
23
## Before execution
24
24
@@ -37,13 +37,13 @@ Instance Readiness Testing (IRT) is a framework built to orchestrate real-world
37
37
1.[Optional] Set up a storage account to archive test results over time. For help, see the [instructions](#uploading-results-to-your-own-archive)
38
38
1. Log into Azure, if not already logged in: `az login --use-device`
39
39
* User should have `Contributor` role
40
-
2. Create an Azure Managed Identity for the container to use.
40
+
1. Create an Azure Managed Identity for the container to use.
41
41
* Using the provided script: `MI_RESOURCE_GROUP="<your resource group> MI_NAME="<managed identity name>" SUBSCRIPTION="<subscription>" ./create-managed-identity.sh`
42
42
* Can be created manually via the Azure portal, refer to the script for needed permissions
43
-
3. Create a service principal and security group. The service principal is used as the executor of the test. The group informs the kubernetes cluster of valid users. The service principal must be a part of the security group, so it has the ability to log into the cluster.
43
+
1. Create a service principal and security group. The service principal is used as the executor of the test. The group informs the kubernetes cluster of valid users. The service principal must be a part of the security group, so it has the ability to log into the cluster.
44
44
* You can provide your own, or use our provided script, here's an example of how it could be executed; `AAD_GROUP_NAME=external-test-aad-group-8 SERVICE_PRINCIPAL_NAME=external-test-sp-8 ./irt/create-service-principal.sh`
45
45
* This script prints four key/value pairs for you to include in your input file.
46
-
4. If necessary, create the isolation domains required to execute the tests. They aren't lifecycled as part of this test scenario.
46
+
1. If necessary, create the isolation domains required to execute the tests. They aren't lifecycled as part of this test scenario.
47
47
***Note:** if deploying isolation domains, your network blueprint must define at least one external network per isolation domain. see `networks-blueprint.example.yml` for help with configuring your network blueprint.
48
48
*`create-l3-isolation-domains.sh` takes one parameter, a path to your networks blueprint file; here's an example of the script being invoked:
0 commit comments