OUTSCALE Kubernetes as a Service
Managed Kubernetes clusters with an OUTSCALE-run control plane and worker node pools.
- Provider
- outscale
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoUpgrade | boolean | — | no | false | inherited |
| autoscaling | boolean | — | no | false | inherited |
| controlPlaneHighlyAvailable | boolean | — | no | false | inherited |
| controlPlaneType | enum | cp.mono.master | cp.3.masters.small | cp.3.masters.medium | cp.3.masters.large | no | cp.mono.master | inherited |
| managed | boolean | — | no | false | ▸ true |
| networkPolicy | boolean | — | no | — | inherited |
| nodeCount | integer | — | no | — | inherited |
| nodePools | integer | — | no | — | inherited |
| privateControlPlane | boolean | — | no | — | inherited |
| rbac | boolean | — | no | — | inherited |
| 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: "oks", component: "outscale-oks" }Container Service for Kubernetesalibaba-ackAmazon 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-zun
# yaml-language-server: $schema=../../schema/component.schema.json # OUTSCALE Kubernetes as a Service (OKS): "a managed Kubernetes service designed for efficiency # and ease of use" ("About OKS"). 3DS OUTSCALE runs the control plane and applies version and # security updates to it; the entry-level `cp.mono.master` control plane has a single master # with no high availability and no SLA, while the `cp.3.masters.*` types run three masters. # Worker nodes are always organised into node pools, and clusters are upgraded manually across # the supported versions 1.30 to 1.35. schemaVersion: "1" type: "component" id: "outscale-oks" kind: "container-orchestrator" provider: "outscale" docs: "https://docs.outscale.com/en/userguide/About-OKS.html" defaults: managed: true properties: controlPlaneType: type: "enum" values: ["cp.mono.master", "cp.3.masters.small", "cp.3.masters.medium", "cp.3.masters.large"] default: "cp.mono.master" controlPlaneHighlyAvailable: type: "boolean" default: false nodePools: type: "integer" autoUpgrade: type: "boolean" default: false