Check Item
- Check whether the nodes are running properly.
- Check whether the node network is normal.
- Check whether the container network is normal.
Procedure
The node status reflects whether the node component or network is normal.
Go to the CCE console and access the cluster console. Choose Nodes in the navigation pane. You can filter node status by status to check whether there are abnormal nodes.
The container network affects services. Check whether your services are available.
Solution
If the node status is abnormal, contact technical support.
If the container network is abnormal and your services are affected, contact technical support and confirm the abnormal network access path.
Source |
Destination |
Destination Type |
Possible Fault |
|---|---|---|---|
|
Public IP address of Service ELB |
Cluster traffic load balancing entry |
No record. |
Private IP address of Service ELB |
Cluster traffic load balancing entry |
No record. |
|
Public IP address of ingress ELB |
Cluster traffic load balancing entry |
No record. |
|
Private IP address of ingress ELB |
Cluster traffic load balancing entry |
No record. |
|
Public IP address of NodePort Service |
Cluster traffic entry |
The kube proxy configuration is overwritten. This fault has been rectified in the upgrade process. |
|
Private IP address of NodePort Service |
Cluster traffic entry |
No record. |
|
ClusterIP Service |
Service network plane |
No record. |
|
Non NodePort Service port |
Container network |
No record. |
|
Cross-node pods |
Container network plane |
No record. |
|
Pods on the same node |
Container network plane |
No record. |
|
Service and pod domain names are resolved by CoreDNS. |
Domain name resolution |
No record. |
|
External domain names are resolved based on the CoreDNS hosts configuration. |
Domain name resolution |
After the coredns add-on is upgraded, the configuration is overwritten. This fault has been rectified in the add-on upgrade process. |
|
External domain names are resolved based on the CoreDNS upstream server. |
Domain name resolution |
After the coredns add-on is upgraded, the configuration is overwritten. This fault has been rectified in the add-on upgrade process. |
|
External domain names are not resolved by CoreDNS. |
Domain name resolution |
No record. |