Score:0

Rancher Cluster Error: writing to invalid external IP

za flag

After restarting an ETCD, the cluster remains in Error state. The kube-apiserver (i think) is trying to connect to an invalid public IP Address.

The frontend shows this:

This cluster is currently Error; areas that interact directly with it will not be available until the API is ready.

Failed to ensure monitoring project name: failed to find "cattle-prometheus" Namespace: Get "https://INTERNAL-IP:6443/api/v1/namespaces/cattle-prometheus": write tcp 172.17.0.2:443->PUBLIC-IP:36343: i/o timeout

While in the rancher logs a whole set of errors appear, all about trying to connect to the same public IP Address.

How do I figure out why it's attempting to connect to the external address, instead of an Internal Address, and how do I fix it?

kubelet-preferred-address-types is set to InternalIP,ExternalIP,Hostname - does this affect the selection of the IP address it's trying to connect to?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.