KubeNodeConfig

apiVersion: v1alpha1
kind: KubeNodeConfig
registerWithFQDN: true # The `registerWithFQDN` field is used to force kubelet to use the node FQDN for registration.
# The `nodeIP` field is used to configure `--node-ip` flag for the kubelet.
nodeIP:
    # The `validSubnets` field configures the networks to pick kubelet node IP from.
    validSubnets:
        - 10.0.0.0/8
        - '!10.0.0.3/32'
        - fdc7::/16
# Configures the node labels for the machine.
labels:
    examplelabel: examplevalue
# Configures the node annotations for the machine.
annotations:
    customer.io/rack: r13a25
# Configures the node taints for the machine. Effect is optional.
taints:
    exampletaint: examplevalue:NoSchedule

Field	Type	Description	Value(s)
`skipNodeRegistration`	bool	The `skipNodeRegistration` is used to run the kubelet without registering with the apiserver. This runs kubelet as standalone and only runs static pods. When this is set to true, other fields in this document are ignored.	`true` `yes` `false` `no`
`registerWithFQDN`	bool	The `registerWithFQDN` field is used to force kubelet to use the node FQDN for registration. This is required in clouds like AWS.	`true` `yes` `false` `no`
`nodeIP`	NodeIPConfig	The `nodeIP` field is used to configure `--node-ip` flag for the kubelet. This field should be set when a node has multiple addresses to choose from.
`labels`	map[string]string	Configures the node labels for the machine. Note: In the default Kubernetes configuration, worker nodes are restricted to set labels with some prefixes (see NodeRestriction admission plugin).
`annotations`	map[string]string	Configures the node annotations for the machine.
`taints`	map[string]string	Configures the node taints for the machine. Effect is optional. Note: In the default Kubernetes configuration, worker nodes are not allowed to modify the taints (see NodeRestriction admission plugin).

nodeIP

NodeIPConfig represents the node IP configuration.

Field	Type	Description	Value(s)
`validSubnets`	[]string	The `validSubnets` field configures the networks to pick kubelet node IP from. For dual stack configuration, there should be two subnets: one for IPv4, another for IPv6. IPs can be excluded from the list by using negative match with `!`, e.g `!10.0.0.0/8`. Negative subnet matches should be specified last to filter out IPs picked by positive matches. If not specified, node IP is picked based on cluster podCIDRs: IPv4/IPv6 address or both.

KubeNetworkConfig

KubePrismConfig

⌘I

Overview

Getting Started

Platform specific installation

Deploying and managing workloads

Networking

Security

Build and extend Talos

Configure your Talos cluster

Advanced guides

Reference

Troubleshooting and support

Learn more

nodeIP

​nodeIP

nodeIP