Red Hat OpenShift
Container orchestratoropenshift
Red Hat's Kubernetes platform with OVN-Kubernetes networking, security context constraints and an integrated registry.
- Provider
- default
- Category
- Compute
- Also known as
- OCP
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoscaling | boolean | — | no | false | ▸ false |
| integratedRegistry | boolean | — | no | true | inherited |
| machineAutoscaler | boolean | — | no | false | inherited |
| managed | boolean | — | no | false | ▸ false |
| networkPlugin | enum | ovn-kubernetes | openshift-sdn | no | ovn-kubernetes | inherited |
| networkPolicy | boolean | — | no | — | ▸ true |
| nodeCount | integer | — | no | — | inherited |
| privateControlPlane | boolean | — | no | — | inherited |
| rbac | boolean | — | no | — | ▸ true |
| securityContextConstraints | boolean | — | no | true | 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: "openshift", component: "openshift" }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 NomadnomadRancherrancherDigitalOcean 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 # Red Hat OpenShift Container Platform. Per "Using RBAC to define and apply permissions" RBAC with default # cluster and local roles governs every action, and per the networking guide OVN-Kubernetes is the default # network plugin, so NetworkPolicy is enforced as soon as a policy is written. schemaVersion: "1" type: "component" id: "openshift" kind: "container-orchestrator" provider: "default" docs: "https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/authentication_and_authorization/using-rbac" aliases: ["OCP"] defaults: managed: false autoscaling: false rbac: true networkPolicy: true properties: networkPlugin: type: "enum" values: ["ovn-kubernetes", "openshift-sdn"] default: "ovn-kubernetes" securityContextConstraints: type: "boolean" default: true integratedRegistry: type: "boolean" default: true machineAutoscaler: type: "boolean" default: false