During the installation or operation of k8s cluster, you may encounter problems of "error getting node", such as:
"Error getting node" err="node \"master\" not found"
dial tcp 10.8.126.46:6443: connect: connection refused"
"Error getting node" err="node \"master\" not found"
"Error getting node" err="node \"master\" not found"
The way to troubleshoot such problems is to execute the following commands to check the specific error causes:
journalctl -xeu kubelet
Find the initial error and deal with it according to different errors
according to the problems I have encountered, there are mainly the following possibilities:
- No swap memory disabled
- There is a problem with hostname setting or hosts setting (other bloggers listed reasons)
- The container and k8s version is not compatible (other bloggers listed reasons)
Read More:
- The deployment of etcd storage and flannel network configuration for kubernetes / k8s multi node deployment
- K8s deployment of single node Nacos error server is down now, please try again later
- Summary of k8s single master cluster deployment
- Common errors in k8s initialization_ [WARNING NumCPU]_ [WARNING SystemVerification]_ WARNING Hostname
- Error from server (alreadyexists) clusterrolebindings.rbac.authorization .k8s.io “kubelet
- K8s error in installing calico plug-in
- Installation of k8s Helm
- K8s configure HTTPS with existing certificate
- K8s deployment Kafka has been reporting errors.
- for k, v in k_map: ValueError: too many values to unpack (expected 2)
- Uncaught TypeError: Failed to execute ‘appendChild’ on ‘Node’: parameter 1 is not of type ‘Node How to Fix
- How to Fix Node.js connection to MYSQL error.
- How to Disassemble/Assemble Galaxy S4 i9500 for Screen/Parts Repair!
- VUEJS Failed to execute ‘removeChild’ on ‘Node’: The node to be removed is not a child of
- Uncaught TypeError: Failed to execute ‘removeChild’ on ‘Node’: parameter 1 is not of type ‘Node’.
- Solve the problem that node. js USES MySQL to connect econnunion 127.0.0.0.1:3306
- Solve the problem that the local flow of the nifi node is inconsistent with the cluster flow, resulting in the failure to join the cluster
- How to Fix Module build failed: Error: ENOENT: no such file or directory, scandir xxxxxx\node_…
- How to Fix webpack Module build failed Error: The node API for ‘babel’ has been moved to babel-core
- How to Fix SQL Error: 1054, SQLState: 42S22 Unknown column ‘markcardex0_.art_service_time’ in ‘field list’