Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple etcadm nodes tls fail from api-server #397

Open
fontexD opened this issue May 15, 2024 · 0 comments
Open

Multiple etcadm nodes tls fail from api-server #397

fontexD opened this issue May 15, 2024 · 0 comments

Comments

@fontexD
Copy link

fontexD commented May 15, 2024

I have a setup with 3 control-planes and 3 etcd nodes created with etcdadm

the issue is it generates different api-server-etcd-client.crt so i have 3 etcd-api server certs

but on the api-servers in k8s i can only define 1, so 2 of the nodes will get a error with tls of course
how do i come around this issue ? do i need to use a loadblaancer if i want to use mulitple etcd-nodes or ?
id prefer not to

logging.go:59] [core] [Channel #450396 SubChannel #450397] grpc: addrConn.createTransport failed to connect to {Addr: "k8s-etcd-1:2379", ServerName: "k8s-etcd-1:2379", }. Err: connection error: desc = "error reading server preface: read tcp 192.168.1.220:35906->192.168.1.240:2379: use of closed network connection"

btw i tried joining the slack-channel couldt get access, seems i need to be invited ? [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant