Container Service for Kubernetes:Getting started with workflow clusters

Kubernetes clusters for distributed Argo workflows (workflow clusters) are deployed on top of a serverless architecture and runs Argo workflows on elastic container instances. By optimizing cluster parameters and using preemptible elastic container instances, workflow clusters can schedule large-scale workflows with efficiency, elasticity, and cost-effectiveness. This topic describes how to quickly get started with workflow clusters and the usage notes for references.

Getting started

Usage notes for references

Basic features

Feature	References
Create a workflow cluster and obtain the kubeconfig file of the cluster	Create a workflow cluster
Create a workflow	Create a workflow
Access the Argo Server console	Enable Argo Server for a workflow cluster Enable Internet access for Argo Server

Advanced features

Feature	References
Manage workflow clusters	Access the workflow cluster console through a custom domain name Use ApsaraDB RDS for MySQL to migrate large workflows Modify the configuration of a workflow cluster
Manage workflows	Run workflows on a specified type of ECS instances Use volumes Configure artifacts Configure a workflow to pull images from the Container Registry Enterprise Edition instance without a password Use a DingTalk chabot to send event notifications
Eventing	Enable eventing Use Simple Message Queue (formerly MNS) to trigger event-driven workflows Upload objects to OSS to trigger workflows
Observability	Enable Managed Service for Prometheus Configure Simple Log Service

References

• To learn the features, benefits, and network design of workflow clusters and how they work, refer to Overview of Kubernetes clusters for distributed Argo workflows.

• No cluster management fee is charged for workflow clusters. If other Alibaba Cloud services are used when you use workflow clusters, you must pay for these services based on their billing rules. For more information about billing, see ACK One billing.