Container Service for Kubernetes
Managed Kubernetes service that runs the control plane for you across availability zones and leaves you only worker nodes to create.
- Provider
- alibabacloud
- Category
- Compute
- Official docs
- https://www.alibabacloud.com/help/en/ack/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoscaling | boolean | — | no | false | inherited |
| clusterType | enum | ack-basic | ack-pro | ack-serverless | ack-edge | ack-dedicated | no | ack-pro | inherited |
| managed | boolean | — | no | false | ▸ true |
| networkPlugin | enum | flannel | terway | no | — | inherited |
| networkPolicy | boolean | — | no | — | inherited |
| nodeCount | integer | — | no | — | inherited |
| privateControlPlane | boolean | — | no | — | inherited |
| rbac | boolean | — | no | — | ▸ true |
| version | string | — | no | — | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "ack", component: "alibaba-ack" }Amazon Elastic Container Serviceaws-ecsAmazon Elastic Kubernetes Serviceaws-eksRed Hat OpenShift Service on AWSaws-rosaAzure Kubernetes Serviceazure-aksAzure Kubernetes Fleet Managerazure-kubernetes-fleet-managerAzure Red Hat OpenShiftazure-red-hat-openshiftAzure Service Fabricazure-service-fabricCloudflare Containerscloudflare-containersGeneric container orchestratorcontainer-orchestratorCoreWeavecoreweaveDocker Swarmdocker-swarmk0sk0sK3sk3sKarmadakarmadaKuberneteskubernetesMicroK8smicrok8sHashiCorp NomadnomadRed Hat OpenShiftopenshiftRancherrancherDigitalOcean Kubernetesdigitalocean-kubernetesGoogle Distributed Cloud (software only) for bare metalgoogle-distributed-cloud-bare-metalGoogle Distributed Cloud (software only) for VMwaregoogle-distributed-cloud-vmwareGoogle Kubernetes Enginegoogle-gkeGKE Autopilotgoogle-gke-autopilotGKE Enterprise fleetgoogle-gke-enterpriseGKE Multi-Cloudgoogle-gke-multi-cloudCluster Services for OpenShiftgoogle-openshift-cluster-servicesIBM Cloud Kubernetes Serviceibm-kubernetes-serviceRed Hat OpenShift on IBM Cloudibm-openshiftIBM Cloud Satelliteibm-satelliteOCI Kubernetes Engineoci-kubernetes-engineOKE Virtual Node Pooloci-oke-virtual-node-poolOpenStack Magnumopenstack-magnumOpenStack Zunopenstack-zunOUTSCALE Kubernetes as a Serviceoutscale-oks
# yaml-language-server: $schema=../../schema/component.schema.json # Container Service for Kubernetes (ACK): managed Kubernetes clusters where ACK provisions and manages the # master nodes and you create only worker nodes ("What is Container Service for Kubernetes"). That page states # managed clusters come as Basic and Pro, the managed control plane runs at least two kube-apiserver # instances and three etcd instances across availability zones, access control integrates RAM with Kubernetes # RBAC, and the Flannel and Terway plug-ins support network policies. It also records that ACK dedicated # clusters can no longer be created since 2024-08-21 except for CloudBox scenarios. schemaVersion: "1" type: "component" id: "alibaba-ack" kind: "container-orchestrator" provider: "alibabacloud" docs: "https://www.alibabacloud.com/help/en/ack/" defaults: managed: true rbac: true properties: clusterType: type: "enum" values: ["ack-basic", "ack-pro", "ack-serverless", "ack-edge", "ack-dedicated"] default: "ack-pro" networkPlugin: type: "enum" values: ["flannel", "terway"]