All Products
Search
Document Center

Container Service for Kubernetes:How to modify workflow cluster configurations

Last Updated:Mar 26, 2026

After creating a Container Service for Argo Workflows cluster, you can update the data-plane virtual switch (vSwitch), tune the workflow controller, or increase vCPU quotas as your workloads grow.

Modify the data-plane virtual switch

Specify multiple vSwitches to distribute workflow Pods across zones for load balancing. The cluster distributes requests randomly across all specified zones.

Prerequisites

Before you begin, ensure that you have:

Edit vSwitches

  1. Log on to the Container Service for Argo Workflows cluster console and click the name of your cluster.

  2. On the Cluster Information page, click the Basic Information tab. Scroll down to Associated Cloud Resources > vSwitch, then click Edit.

  3. Add or remove vSwitches, then save your changes.

Important

When specifying multiple vSwitches, observe these limits:

  • All vSwitches must be in the same VPC.

  • A maximum of 10 vSwitches are supported.

Configure the workflow-controller-configmap

The workflow-controller-configmap ConfigMap controls the behavior of your Argo Workflows controller. Configure it when you need to:

  • Offload large workflow state data from etcd to PostgreSQL or MySQL

  • Archive completed workflows to an external database for long-term retention and auditing

  • Tune Pod garbage collection settings to reclaim resources faster or slower

For all available fields, see Workflow Controller ConfigMap in the Argo Workflows documentation.

Edit the ConfigMap

Replace CLUSTER_ID with your cluster ID and run the following command:

kubectl edit configmap -n CLUSTER_ID workflow-controller-configmap
Important

The podMetadata block is required for the cluster to function. Do not delete it.

podMetadata:
  labels:
    workflow.xflow.aliyun: xflow
    alibabacloud.com/compute-class: general-purpose
    alibabacloud.com/acs: "true"

Configure ACS quotas

Container Compute Service (ACS) accounts have a small default vCPU quota. If your workflows need more compute capacity, request a quota increase in Quota Center.

For quota limits and how to request increases, see Limits and quotas.