Edit

Limitations and known issues in Chaos Studio workspaces (preview)

This article lists the current limitations of the Azure Chaos Studio workspaces and scenarios public preview, and the known issues to be aware of while you use it. For limitations of the classic experiments model, see Azure Chaos Studio limitations and known issues.

Important

Azure 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:

Limitations

  • Curated scenario catalog. Workspaces run scenario templates and custom scenarios built from them in the designer. The full classic fault library, dynamic targeting, and scheduled runs aren't available in workspaces. The classic experiments model remains available for these capabilities. For a full comparison, see Compare workspaces and experiments.

  • Limited agent-based fault injection. CPU Pressure and Physical Memory Pressure are the only agent-based scenarios in the workspaces preview. They support standalone Windows and Linux virtual machines with a managed identity; virtual machine scale sets and VM sizes that use Arm-based processors aren't supported yet, and the target VM 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 classic experiments with the agent.

  • No AKS-specific fault injection. Workspaces don't yet include Azure Kubernetes Service (AKS) fault injection, such as in-cluster pod faults. You can test the zone resilience of AKS node pools today by scoping a workspace to the cluster's infrastructure resource group. To learn more, see Test workload resiliency on AKS with Chaos Studio. For in-cluster fault injection today, use AKS Chaos Mesh faults in the classic model.

  • 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 private networking configurations for the classic model (agent-based experiments and AKS Chaos Mesh faults) apply to classic experiments only.

  • Workspace creation regions. You can create workspaces only in the supported workspace regions. A workspace can still act on target resources in any Azure region.

  • No customer-managed keys. Workspaces don't support customer-managed keys. To encrypt experiment data with your own keys, use customer-managed keys with classic experiments.

  • Automation and SDK coverage. You can manage workspaces and scenarios with the Azure portal, the az chaos Azure CLI extension, Bicep and ARM templates, the REST API, and the .NET SDK (preview). PowerShell and Terraform don't support workspaces. The current Python and JavaScript SDK versions cover the classic experiments model 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.

Known issues

  • Automatic role assignment fails for service group scopes. For a workspace scoped to a service group, automatic role assignment 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.

Next steps

  • Last updated on