Rancher

Container orchestratorrancher

Management plane that provisions and governs many Kubernetes clusters with central authentication and project-level RBAC.

Provider: default
Kind: Container orchestrator
Category: Compute
Official docs: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac

Properties · 3 set by this component

property	type	values	required	kind default	this component
autoscaling	boolean	—	no	false	▸ false
centralizedAuthentication · component property	boolean	—	no	true	inherited
managed	boolean	—	no	false	▸ false
managesMultipleClusters · component property	boolean	—	no	true	inherited
networkPolicy	boolean	—	no	—	inherited
nodeCount	integer	—	no	—	inherited
privateControlPlane	boolean	—	no	—	inherited
provisionedDistribution · component property	enum	rke2 \| k3s \| imported	no	rke2	inherited
rbac	boolean	—	no	—	▸ true
version	string	—	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: "rancher", component: "rancher" }

Other Container orchestrator products · 35

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Rancher, a management plane for many Kubernetes clusters. Per "Role-Based Access Control (RBAC)" global,
3# cluster and project roles are implemented on top of Kubernetes RBAC and enforced by Kubernetes, so a
4# Rancher-managed estate is RBAC-governed out of the box.
5schemaVersion: "1"
6type: "component"
7id: "rancher"
8kind: "container-orchestrator"
9provider: "default"
10docs: "https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac"
11defaults:
12  managed: false
13  autoscaling: false
14  rbac: true
15properties:
16  managesMultipleClusters:
17    type: "boolean"
18    default: true
19  provisionedDistribution:
20    type: "enum"
21    values: ["rke2", "k3s", "imported"]
22    default: "rke2"
23  centralizedAuthentication:
24    type: "boolean"
25    default: true

The same page as markdown, for an agent: /catalogue/components/rancher.md