adamant-kite-43734
11/17/2022, 8:54 AMadamant-kite-43734
11/17/2022, 12:16 PMbland-translator-58922
11/17/2022, 1:04 PMflat-translator-32204
11/17/2022, 4:51 PMwget: unable to resolve host address
however upon logging onto that pod and trying to ping 8.8.8.8, the packets are being transmitted successfully.
bash-4.3# ping <http://google.com|google.com>
ping: bad address '<http://google.com|google.com>'
bash-4.3# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=49 time=1.133 ms
64 bytes from 8.8.8.8: seq=1 ttl=49 time=1.084 ms
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.083/1.109/1.137 ms
bash-4.3#
Note:
1. Security groups are proper with access to all http traffic.
So I am not sure why the DNS resolution is failing on the EC2 instances.
I have tried restarting coredns service sudo kubectl -n kube-system rollout restart deployment coredns
and it temporarily fixes the issue but when I delete and recreate the pod, I again see issue with DNS resolution.
Please let me know of there is anything needs to be changed in config files or is there any setup issue.adamant-kite-43734
11/17/2022, 7:34 PMadamant-kite-43734
11/17/2022, 10:14 PMgifted-breakfast-73755
11/17/2022, 10:15 PMetcd
node on port 22 but not on port 2379, yet I can telnet 10.10.50.44 2379
from the etcd
node itself (10.10.50.44
)adamant-kite-43734
11/17/2022, 11:18 PMadamant-kite-43734
11/18/2022, 2:05 AMbreezy-ram-80329
11/18/2022, 3:45 AMadamant-kite-43734
11/18/2022, 7:10 AMsilly-jordan-81965
11/18/2022, 8:58 AMimportant-toddler-21468
11/18/2022, 9:41 AMadamant-kite-43734
11/18/2022, 10:20 AMadamant-kite-43734
11/18/2022, 11:28 AMadamant-kite-43734
11/18/2022, 3:39 PMastonishing-glass-5106
11/18/2022, 3:45 PMadamant-kite-43734
11/18/2022, 5:46 PMadamant-kite-43734
11/19/2022, 1:39 AMagreeable-pager-80720
11/20/2022, 9:59 AMkubectl
with a downstream cluster.
I have fetched the kubeconfig with rancher cli: rancher clusters kubeconfig CLUSTER-ID CLUSTER-NAME > kubeconfig
kubectl
commands fail with Unable to connect to the server: x509: certificate signed by unknown authority
where should I look into to find the problem? which certificate is it talking about?
is this related to the contents of clusters.*.cluster.certificate-authority-data
in the kubeconfig file?polite-king-74071
11/20/2022, 4:20 PMpolite-king-74071
11/20/2022, 4:21 PMadamant-kite-43734
11/20/2022, 4:22 PMwide-gold-24295
11/20/2022, 5:31 PMwide-gold-24295
11/20/2022, 5:32 PMwide-gold-24295
11/20/2022, 5:32 PMadamant-kite-43734
11/20/2022, 5:33 PMbland-translator-58922
11/21/2022, 9:21 AMmost-holiday-75301
11/21/2022, 9:22 AMCATTLE_UI_PRIMARY_COLOR
environment variable isn't supposed to change the --primary
CSS var? Although in /v3/settings/ui-primary-color
it looks set, no actual color change happens (Rancher v2.6.8).adamant-kite-43734
11/21/2022, 1:18 PM