From 8189e7765ea62af5109fdd28aa4d2038434579ae Mon Sep 17 00:00:00 2001 From: msarage-ux Date: Wed, 2 Sep 2026 12:15:03 +0530 Subject: [PATCH] Add DNS resolver and routes to node addition YAML example Update the nodes-config.yaml example to include DNS resolver and routes configuration, which are required for successful node addition. Also document that CSRs must be approved twice during the node addition process. Changes: - Added dns-resolver section with server and search configuration - Added routes section with default gateway configuration - Added IMPORTANT note about double CSR approval requirement - Clarified that first CSR is for kubelet client certificate - Clarified that second CSR is for kubelet serving certificate The missing DNS configuration was causing node join failures. These additions ensure users have a complete working example. Fixes: OSDOCS-15544 Co-Authored-By: Claude Sonnet 4.5 --- modules/adding-node-iso-yaml.adoc | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/modules/adding-node-iso-yaml.adoc b/modules/adding-node-iso-yaml.adoc index b0efd82c867..f9e60c7c2c5 100644 --- a/modules/adding-node-iso-yaml.adoc +++ b/modules/adding-node-iso-yaml.adoc @@ -44,6 +44,17 @@ hosts: - ip: 192.168.122.2 prefix-length: 23 dhcp: false + dns-resolver: + config: + server: + - 192.168.122.1 + search: + - example.com + routes: + config: + - destination: 0.0.0.0/0 + next-hop-address: 192.168.122.1 + next-hop-interface: eth0 - hostname: extra-worker-2 rootDeviceHints: deviceName: /dev/sda @@ -62,6 +73,17 @@ hosts: - ip: 192.168.122.3 prefix-length: 23 dhcp: false + dns-resolver: + config: + server: + - 192.168.122.1 + search: + - example.com + routes: + config: + - destination: 0.0.0.0/0 + next-hop-address: 192.168.122.1 + next-hop-interface: eth0 ---- . Generate the ISO image by running the following command: @@ -110,3 +132,8 @@ If these checks are skipped, you must manually check for CSRs by running the `oc ---- $ oc adm certificate approve ---- ++ +[IMPORTANT] +==== +Each node requires two CSR approvals during the addition process. The first CSR is for the kubelet client certificate, and the second CSR is for the kubelet serving certificate. You must approve both CSRs for each node to complete the node addition successfully. +====