Log in

Sangfor Support Center

Table of Contents
< All Topics
Print

How to troubleshoot: Failed to deploy k8s cluster: Control interface is not ready

Posted
Updated
Byadmin
Views5

Problem Description

Deployment of k8s cluster failed: controller node not ready

image

Alert Information

Deployment failed, control panel status: controller node not ready

Effective Troubleshooting Steps

SKE's Kubernetes cluster has a network requirement to be able to access SKE's internal communication port.

Have the customer provide two screenshots:

  1. [SKE Interface] Deployment failure cluster's [Cluster Networking] – [Basics]

image

  1. [SCP Interface] – [Shared Service Network] – [Kubernetes Engine (SKE)]

image

From the image, it can be seen that the 192.168.80.x k8s nodes cannot access the [SKE Internal Communication Port] 10.1.1.10, so the deployment fails.

Solution:

Delete the cluster and use [Isolation Mode Deployment].

Management network: use 10.1.1.x

Business network: use 192.168.80.x

Root Cause

Most likely network connectivity or VLAN issues.

Solution

  1. Refer to the effective troubleshooting steps above, have the customer provide the two screenshots, analyze whether the network is unreachable. If it is, it is recommended to use the [Isolation Mode Deployment]. The configuration is that the management network and the internal communication port are in the same network segment, while the business network uses the customer's original expected network segment.
  2. If the network is found to be reachable but the deployment still fails, log in to the backend of the deployment-failed node. Use the account root and password k8sadmin, and try pinging the internal communication port and testing arping to investigate any potential network issues. It might be due to IP conflicts, VLAN port issues, or network isolation problems.

To check the network, first locate where the internal communication port is. The actual internal communication port is mounted on the router directly connected to the [Kubernetes Engine (SKE)]. Ensure that the device connected to the k8s node management port can access this router. After ensuring the cluster creation can ping through, the deployment will succeed. image

Scope of Impact

NA

Is it a Temporary Solution?

No

Recommendations and Summary

NA

Troubleshooting Content

NA

Original Link

https://support.sangfor.com.cn/cases/list?product_id=37&type=1&category_id=29565&isOpen=true