action Node

create_node

Create one new node in the cluster


Type	action
Module	chaosk8s.node.actions
Name	create_node
Return	kubernetes.client.models.v1_node.V1Node

Usage

JSON

{
  "name": "create-node",
  "type": "action",
  "provider": {
    "type": "python",
    "module": "chaosk8s.node.actions",
    "func": "create_node"
  }
}

YAML

name: create-node
provider:
  func: create_node
  module: chaosk8s.node.actions
  type: python
type: action

Arguments

Name	Type	Default	Required	Title	Description
meta	mapping	null	No	Metadata	The metadata payload for the new node
spec	mapping	null	No	Specification	The specification payload for the new node

Due to the way things work on certain cloud providers, you won’t be able to use this meaningfully on them. For instance on GCE, this will likely fail.

Signature

def create_node(
    meta: Dict[str, Any] = None,
    spec: Dict[str, Any] = None,
    secrets: Dict[str, Dict[str, str]] = None
) -> kubernetes.client.models.v1_node.V1Node:
    pass

Related starters

Kubernetes

action Node

uncordon_node

Uncordon nodes matching the given label name, so that pods can be scheduled on them again
Kubernetes

action Node

delete_nodes

Delete nodes gracefully
Kubernetes

probe Node

nodes_must_be_healthy

Verify a set of conditions against a set of nodes: * FrequentKubeletRestart must be False * FrequentDockerRestart must be False * FrequentContainerdRestart must be False * ReadonlyFilesystem must be False * KernelDeadlock must be False * CorruptDockerOverlay2 must be False * FrequentUnregisterNetDevice must be False * NetworkUnavailable must be False * FrequentKubeletRestart must be False * MemoryPressure must be False * DiskPressure must be False * PIDPressure must be False * Ready must be True

create_node

Related starters

`uncordon_node`

`delete_nodes`

`nodes_must_be_healthy`