Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Review Chaos Studio Workspaces limitations before you select a Scenario or scope a resilience test. This page covers public preview constraints for Scenario coverage, AKS node infrastructure, agent-based Actions, private networking, and automation. The separate Experiments (classic) limitations don't define Workspaces support.
Important
Chaos Studio Workspaces and Scenarios are in public preview. Microsoft provides this preview "as is" and "as available," and it isn't covered by service-level agreements or limited warranty. Microsoft provides customer support for the preview on a best-effort basis. This preview isn't meant for production use. For more information, see the following articles:
The Chaos Studio extension for AKS has a separate, limited preview for allow-listed subscriptions. The Workspaces public preview doesn't give you access to the extension.
Limitations
Curated Scenario catalog. Workspaces run Scenario templates and custom Scenarios built from the Actions in those templates and the Actions available for custom Scenarios. The Workspace rejects Actions it doesn't recognize. The full fault and action library for Experiments (classic), dynamic targeting, and scheduled experiment runs aren't available in Workspaces. Use Experiments (classic) for these capabilities. For a full comparison, see Choose between Chaos Studio Workspaces and Experiments (classic).
Limited agent-based fault injection. CPU Pressure and Physical Memory Pressure are the only agent-based Scenarios in the Workspaces preview. They support Windows and Linux virtual machines and virtual machine scale sets with a managed identity. VM sizes that use Arm-based processors aren't supported yet. The target needs public outbound connectivity to the Chaos Studio service. In the Azure portal, these Scenarios appear under My scenarios rather than in the recommended Scenarios list. For details, see Agent-based Scenario requirements. All other in-guest faults, such as network faults and disk pressure, aren't available in Workspaces; for those faults, use the Chaos Studio agent with Experiments (classic).
AKS pod-level tests have separate preview access. The Chaos Studio extension for AKS provides in-cluster pod-level fault execution through Workspaces in a limited preview for allow-listed subscriptions. It offers pod delete, pod CPU hog, pod memory hog, pod network latency, and pod network loss faults. To request access, open an issue in the Chaos Studio GitHub repository. Prepare to use the extension before installation. Node-level testing doesn't require the extension: scope a Workspace to the cluster's infrastructure resource group as described in Test AKS resilience with Chaos Studio Workspaces. A pod disruption isn't an availability-zone outage. AKS Chaos Mesh faults with Experiments (classic) retain their existing workflow and don't require the extension.
Private networking. Service-direct Scenarios execute their Actions through the Azure Resource Manager control plane, so they don't require a Private Link configuration and work with target resources that use private networking. Agent-based Scenarios are the exception: the target VM must be able to reach the Chaos Studio service over public outbound connectivity, and VMs restricted to private networking aren't supported. The AKS extension connects outbound from the cluster to Chaos Studio. For details, see How the extension works. Private networking for Experiments (classic) applies to agent-based experiments and AKS Chaos Mesh faults.
Workspace creation regions. You can create Workspaces only in the supported Workspace regions. A Workspace can still act on target resources in other Azure regions, subject to the requirements of the Scenario and target. This regional scope doesn't establish availability of the AKS extension preview.
No customer-managed keys. Workspaces don't support customer-managed keys. To encrypt experiment data with your own keys, use customer-managed keys with Experiments (classic).
Automation and SDK coverage. You can manage Workspaces and Scenarios with the Azure portal, the
az chaosAzure CLI extension, Bicep and ARM templates, the REST API, and the .NET SDK (preview). PowerShell doesn't support Workspaces, and the HashiCorp AzureRM provider doesn't expose native resources for Workspaces or Scenarios. Terraform users can deploy and manage these ARM resources with the Azure AzAPI provider: Workspaces, Scenarios, and Scenario configurations. The current Python and JavaScript SDK versions cover Experiments (classic) only, and there's no Java SDK.Per-Scenario constraints. Some Scenarios have their own requirements, such as Windows-only support for the Cache Stampede with Process Crash Scenario. See the notes on each Scenario in Scenarios in Azure Chaos Studio. General Workspace tooling and SDK coverage don't establish support for extension-specific operations; use the instructions for your approved extension preview version.
Known issues
Fix Permissions fails for service group scopes. For a Workspace scoped to a service group, the Fix Permissions option might fail or report that it can't fix missing permissions. Assign the required roles manually as a workaround. See Troubleshoot Workspaces and Scenarios.
Transient portal issues in the Scenario designer and My scenarios. The portal experience is updated frequently during the preview, and you might occasionally encounter transient issues when editing or configuring Scenarios. See Troubleshoot Workspaces and Scenarios for workarounds.
To report an issue or request a capability, use the Chaos Studio community feedback repository.
Report issues and request features
Azure Chaos Studio is developed in the open. To report a bug, request a feature, or ask a question about Workspaces, Scenarios, or the Azure CLI extension, open an issue in the Chaos Studio repository on GitHub. By filing an issue, you can track its progress and see requests from other customers.