new 3 control plane setup with vmware workstation #9182
-
|
Hi Besides talos cluster on physical HPE i'm also testing it inside VMware workstation. ma@localhost vmamd1]$ talosctl config contexts when i try to get members i got this [ma@localhost vmamd1]$ talosctl get members -n 10.99.100.132 all three control planes are in this state
I believe i'm missing sth with certificates, any idea? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
|
Yes, this is a conflict on the host IPs and Kubernetes pod/service CIDRs. You need to change one or another so that they don't overlap. |
Beta Was this translation helpful? Give feedback.
-
|
this is ok now. got another issue though :) ma@localhost vmamd1]$ talosctl get members -n 10.99.100.132 nodes are using external dns, the machine from which i'm configuring cluster some internal DNS, not it seems like i should also do some configuration on dns, reading manual again |
Beta Was this translation helpful? Give feedback.
-
|
Please open separate discussions for separate issues, so that they are better discoverable via the search. In this case it seems to be your DNS server not working properly (?). I don't know what |
Beta Was this translation helpful? Give feedback.
-
|
on machine I'm running talosctl i've changed DNS from 10.99.100.15 to 1.1.1.1
now i'm getting
rpc error: code = Unavailable desc = last connection error: connection error: desc = "transport: Error while dialing: dial tcp: lookup nodes on 1.1.1.1:53: no such host"
it seems i should use internal and setup some zone or ?
just need direction what to do, will open new case if another issue besides DNS will arrise.
Best regards, s prijaznimi pozdravi
Matjaž Antloga, Ortoscale d.o.o.
…________________________________
From: Andrey Smirnov ***@***.***>
Sent: Thursday, August 15, 2024 12:27 PM
To: siderolabs/talos ***@***.***>
Cc: Matjaž Antloga - Ortoscale ***@***.***>; Author ***@***.***>
Subject: Re: [siderolabs/talos] new 3 control plane setup with vmware workstation (Discussion #9182)
Please open separate discussions for separate issues, so that they are better discoverable via the search.
In this case it seems to be your DNS server not working properly (?). I don't know what 10.99.202.15:53 is in your environment.
—
Reply to this email directly, view it on GitHub<#9182 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AR5G3FKJNI5T7H7CDZ4CGWLZRR67LAVCNFSM6AAAAABMR5BMJOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZUGYYTKMQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
i will open new one. ok. |
Beta Was this translation helpful? Give feedback.
Yes, this is a conflict on the host IPs and Kubernetes pod/service CIDRs.
You need to change one or another so that they don't overlap.