Skip to content

Commit 9db5508

Browse files
Merge pull request #263479 from nikhilkaul-msft/new-year-updates
New year updates
2 parents dcf21e6 + 60feebe commit 9db5508

File tree

4 files changed

+40
-9
lines changed

4 files changed

+40
-9
lines changed

articles/chaos-studio/chaos-studio-configure-customer-managed-keys.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Configure customer-managed keys (preview) for experiment encryption
2+
title: Configure customer-managed keys [preview] for experiment encryption
33
titleSuffix: Azure Chaos Studio
44
description: Learn how to configure customer-managed keys (preview) for your Azure Chaos Studio experiment resource using Azure Blob Storage
55
services: chaos-studio
@@ -10,7 +10,7 @@ ms.date: 10/06/2023
1010
ms.topic: how-to
1111
---
1212

13-
# Configure customer-managed keys (preview) for Azure Chaos Studio using Azure Blob Storage
13+
# Configure customer-managed keys [preview] for Azure Chaos Studio using Azure Blob Storage
1414

1515
Azure Chaos Studio automatically encrypts all data stored in your experiment resource with keys that Microsoft provides (service-managed keys). As an optional feature, you can add a second layer of security by also providing your own (customer-managed) encryption key(s). Customer-managed keys offer greater flexibility for controlling access and key-rotation policies.
1616

articles/chaos-studio/chaos-studio-private-link-agent-service.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,8 @@ ms.author: nikhilkaul
99
ms.service: chaos-studio
1010
ms.custom: ignite-fall-2023
1111
---
12-
# How-to: Configure Private Link for Agent-Based experiments
13-
This guide explains the steps needed to configure Private Link for a Chaos Studio **Agent-based** Experiment. The current user experience is based on the private endpoints support enabled as part of public preview of the private endpoints feature. Expect this experience to evolve with time as the feature is enhanced to GA quality.
12+
# How-to: Configure Private Link for Agent-Based experiments [Preview]
13+
This guide explains the steps needed to configure Private Link for a Chaos Studio **Agent-based** Experiment [Preview]. The current user experience is based on the private endpoints support enabled as part of public preview of the private endpoints feature. Expect this experience to evolve with time as the feature is enhanced to GA quality, as it is currently in **preview**.
1414

1515
---
1616
## Prerequisites
@@ -234,6 +234,8 @@ Example of updated agentInstanceConfig.json:
234234

235235
**IF** you blocked outbound access to Microsoft Certificate Revocation List (CRL) verification endpoints, then you need to update agentSettings.JSON to disable CRL verification check in the agent.
236236

237+
By default this field is set to **true**, so you can either remove this field or set the value to false. See [here](chaos-studio-tutorial-agent-based-cli.md) for more details.
238+
237239
```
238240
"communicationApi": {
239241
"checkCertRevocation": false

articles/chaos-studio/chaos-studio-private-networking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Currently, you can only enable certain resource types for Chaos Studio virtual n
2727
To use Chaos Studio with virtual network injection, you must meet the following requirements.
2828
1. The `Microsoft.ContainerInstance` and `Microsoft.Relay` resource providers must be registered with your subscription.
2929
1. The virtual network where Chaos Studio resources will be injected must have two subnets: a container subnet and a relay subnet. A container subnet is used for the Chaos Studio containers that will be injected into your private network. A relay subnet is used to forward communication from Chaos Studio to the containers inside the private network.
30-
1. Both subnets need at least `/28` in the address space. An example is an address prefix of `10.0.0.0/28` or `10.0.0.0/24`.
30+
1. Both subnets need at least `/27` in the address space. An example is an address prefix of `10.0.0.0/28` or `10.0.0.0/24`.
3131
1. The container subnet must be delegated to `Microsoft.ContainerInstance/containerGroups`.
3232
1. The subnets can be arbitrarily named, but we recommend `ChaosStudioContainerSubnet` and `ChaosStudioRelaySubnet`.
3333
1. When you enable the desired resource as a target so that you can use it in Chaos Studio experiments, the following properties must be set:

articles/chaos-studio/chaos-studio-tutorial-agent-based-cli.md

Lines changed: 33 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -113,32 +113,61 @@ The chaos agent is an application that runs in your VM or virtual machine scale
113113

114114
1. Install the Chaos Studio VM extension. Replace `$VM_RESOURCE_ID` with the resource ID of your VM or replace `$SUBSCRIPTION_ID`, `$RESOURCE_GROUP`, and `$VMSS_NAME` with those properties for your virtual machine scale set. Replace `$AGENT_PROFILE_ID` with the agent Profile ID. Replace `$USER_IDENTITY_CLIENT_ID` with the client ID of your managed identity. Replace `$APP_INSIGHTS_KEY` with your Application Insights instrumentation key. If you aren't using Application Insights, remove that key/value pair.
115115

116+
#### Full list of default Agent virtual machine extension configuration
117+
118+
Here is the **minimum agent vm extension configuration** required by the user:
119+
120+
```azcli-interactive
121+
{
122+
"profile": "$AGENT_PROFILE_ID",
123+
"auth.msi.clientid": "$USER_IDENTITY_CLIENT_ID"
124+
}
125+
```
126+
127+
Here is **all values for agent vm extension configuration**
128+
129+
```azcli-interactive
130+
{
131+
"profile": "$AGENT_PROFILE_ID",
132+
"auth.msi.clientid": "$USER_IDENTITY_CLIENT_ID",
133+
"appinsightskey": "$APP_INSIGHTS_KEY",
134+
"overrides": {
135+
"region": string, default to be null
136+
"logLevel": {
137+
"default" : string , default to be Information
138+
},
139+
"checkCertRevocation": boolean, default to be false.
140+
}
141+
}
142+
```
143+
144+
116145
#### Install the agent on a virtual machine
117146

118147
Windows
119148

120149
```azurecli-interactive
121-
az vm extension set --ids $VM_RESOURCE_ID --name ChaosWindowsAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"}'
150+
az vm extension set --ids $VM_RESOURCE_ID --name ChaosWindowsAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"{"Overrides": "CheckCertRevocation" = true}}'
122151
```
123152

124153
Linux
125154

126155
```azurecli-interactive
127-
az vm extension set --ids $VM_RESOURCE_ID --name ChaosLinuxAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"}'
156+
az vm extension set --ids $VM_RESOURCE_ID --name ChaosLinuxAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"{"Overrides": "CheckCertRevocation" = true}}'
128157
```
129158

130159
#### Install the agent on a virtual machine scale set
131160

132161
Windows
133162

134163
```azurecli-interactive
135-
az vmss extension set --subscription $SUBSCRIPTION_ID --resource-group $RESOURCE_GROUP --vmss-name $VMSS_NAME --name ChaosWindowsAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"}'
164+
az vmss extension set --subscription $SUBSCRIPTION_ID --resource-group $RESOURCE_GROUP --vmss-name $VMSS_NAME --name ChaosWindowsAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"{"Overrides": "CheckCertRevocation" = true}}'
136165
```
137166

138167
Linux
139168

140169
```azurecli-interactive
141-
az vmss extension set --subscription $SUBSCRIPTION_ID --resource-group $RESOURCE_GROUP --vmss-name $VMSS_NAME --name ChaosLinuxAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"}'
170+
az vmss extension set --subscription $SUBSCRIPTION_ID --resource-group $RESOURCE_GROUP --vmss-name $VMSS_NAME --name ChaosLinuxAgent --publisher Microsoft.Azure.Chaos --version 1.0 --settings '{"profile": "$AGENT_PROFILE_ID", "auth.msi.clientid":"$USER_IDENTITY_CLIENT_ID", "appinsightskey":"$APP_INSIGHTS_KEY"{"Overrides": "CheckCertRevocation" = true}}'
142171
```
143172
1. If you're setting up a virtual machine scale set, verify that the instances were upgraded to the latest model. If needed, upgrade all instances in the model.
144173

0 commit comments

Comments
 (0)