IBM Cloud Kubernetes Service

ibm Container orchestratoribm-kubernetes-service

Managed Kubernetes cluster whose three-replica master IBM runs, with access mapped from IAM roles onto Kubernetes RBAC.

Provider: ibm
Kind: Container orchestrator
Category: Compute
Official docs: https://cloud.ibm.com/docs/containers
Also known as: IKS

Properties · 2 set by this component

property	type	values	required	kind default	this component
autoscaling	boolean	—	no	false	inherited
infrastructure · component property	enum	vpc \| classic \| satellite	no	—	inherited
managed	boolean	—	no	false	▸ true
masterReplicas · component property	integer	—	no	3	inherited
networkPolicy	boolean	—	no	—	inherited
nodeCount	integer	—	no	—	inherited
privateControlPlane	boolean	—	no	—	inherited
rbac	boolean	—	no	—	▸ true
version	string	—	no	—	inherited
zoneSpread · component property	enum	single-zone \| multizone	no	—	inherited

Rules that apply · 1

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 redundancyerror

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

Use it in a design

nodes:
  - { id: "kubernetes-service", component: "ibm-kubernetes-service" }

Other Container orchestrator products · 35

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# IBM Cloud Kubernetes Service: a "fully managed Kubernetes master that is continuously monitored
3# and updated by IBM", provisioned with three replicas for high availability and spread across
4# zones in a multizone metro ("Understanding IBM Cloud Kubernetes Service"). The same page states
5# that cluster access uses "IBM Cloud IAM service access roles, which correspond with Kubernetes
6# RBAC roles", and that clusters run on VPC, classic or Satellite infrastructure. The default
7# service endpoint exposure is not documented, so privateControlPlane is left unset.
8schemaVersion: "1"
9type: "component"
10id: "ibm-kubernetes-service"
11kind: "container-orchestrator"
12provider: "ibm"
13docs: "https://cloud.ibm.com/docs/containers"
14aliases: ["IKS"]
15defaults:
16  managed: true
17  rbac: true
18properties:
19  infrastructure:
20    type: "enum"
21    values: ["vpc", "classic", "satellite"]
22  zoneSpread:
23    type: "enum"
24    values: ["single-zone", "multizone"]
25  masterReplicas:
26    type: "integer"
27    default: 3

The same page as markdown, for an agent: /catalogue/components/ibm-kubernetes-service.md