GitHub user guillemtp added a comment to the discussion: Kubernets CKS cluster in VMWare integration with Shared Network.
I've checked that no iptables rules could affect to communication to manager server. All rules are opened by default. I've made a small progress. After the node tries to start and the k8s cluster ends with error, If I restart the k8s node I can access to it by the User SSH key. If I check the logs, I can see in cloud-init-output.log the following: ``` 2026-03-16 07:11:37,376 - url_helper.py[WARNING]: Calling 'None' failed [50/120s]: request error [HTTPConnectionPool(host='172.24.35.245', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f7e92d43510>, 'Connection to 172.24.35.245 timed out. (connect timeout=50.0)'))] 2026-03-16 07:12:46,446 - url_helper.py[WARNING]: Calling 'None' failed [119/120s]: request error [HTTPConnectionPool(host='172.24.35.245', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f7e92d4e490>, 'Connection to 172.24.35.245 timed out. (connect timeout=68.0)'))] 2026-03-16 07:12:47,447 - url_helper.py[ERROR]: Timed out, no response from urls: ['http://172.24.35.245/latest/meta-data/instance-id'] 2026-03-16 07:12:47,447 - DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://172.24.35.245/latest/meta-data/instance-id'] after 120 seconds 2026-03-16 07:12:47,447 - util.py[WARNING]: No instance datasource found! Likely bad things to come! 2026-03-16 07:12:47,518 - activators.py[WARNING]: Running ['ifup', 'eth0'] resulted in stderr output: ifup: interface eth0 already configured ``` The IP 172.24.35.245 is the virtual router. A curl to there or also from the controller node, it doesn't work. However, it works to curl to the other VirtualRouter IP 172.24.35.183 <img width="498" height="497" alt="image" src="https://github.com/user-attachments/assets/424e1a98-dc0a-4a9b-8611-2bcbcd188900"; /> I don't see the error in the controller node. I would bet the controller is pointing to 183 instead of 245, but I don't know. I attach the involved logs by controller and the worker [vcenter-log.zip](https://github.com/user-attachments/files/26023846/vcenter-log.zip) GitHub link: https://github.com/apache/cloudstack/discussions/12698#discussioncomment-16158979 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
