OKE Virtual Node Pool

oci Container orchestratoroci-oke-virtual-node-pool

Serverless Kubernetes nodes billed per pod and patched by Oracle.

Provider: oci
Kind: Container orchestrator
Category: Compute
Official docs: https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengcomparingvirtualwithmanagednodes_topic.htm

Properties · 2 set by this component

property	type	values	required	kind default	this component
autoscaling	boolean	—	no	false	▸ false
billingModel · component property	enum	per-pod \| per-node	no	per-pod	inherited
clusterAutoscalerSupported · component property	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
maxPodsPerVirtualNode · component property	integer	—	no	1000	inherited
networkPolicy	boolean	—	no	—	inherited
nodeCount	integer	—	no	—	inherited
podNetworking · component property	enum	vcn-native-pod-networking	no	vcn-native-pod-networking	inherited
privateControlPlane	boolean	—	no	—	inherited
rbac	boolean	—	no	—	inherited
requiresEnhancedCluster · component property	boolean	—	no	true	inherited
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: "oke-virtual-node-pool", component: "oci-oke-virtual-node-pool" }

Other Container orchestrator products · 35

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# OKE virtual node pool: serverless Kubernetes nodes whose data plane Oracle patches and upgrades,
3# billed per pod ("Comparing Virtual Nodes with Managed Nodes"). That page allows virtual nodes
4# only in enhanced clusters, requires the VCN-native pod networking CNI, scales a virtual node to
5# 1,000 pods and rules out the Kubernetes Cluster Autoscaler.
6schemaVersion: "1"
7type: "component"
8id: "oci-oke-virtual-node-pool"
9kind: "container-orchestrator"
10provider: "oci"
11docs: "https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengcomparingvirtualwithmanagednodes_topic.htm"
12defaults:
13  managed: true
14  autoscaling: false
15properties:
16  requiresEnhancedCluster:
17    type: "boolean"
18    default: true
19  podNetworking:
20    type: "enum"
21    values: ["vcn-native-pod-networking"]
22    default: "vcn-native-pod-networking"
23  maxPodsPerVirtualNode:
24    type: "integer"
25    default: 1000
26  billingModel:
27    type: "enum"
28    values: ["per-pod", "per-node"]
29    default: "per-pod"
30  clusterAutoscalerSupported:
31    type: "boolean"
32    default: false

The same page as markdown, for an agent: /catalogue/components/oci-oke-virtual-node-pool.md