-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
TLS handshake remote error: tls: bad certificate #10252
Comments
You redacted the certificate checksum portion of the token, but left the actual passphrase that is used to join the cluster.
Don't do that. This tells the nodes to advertise the load-balancer address, instead of their actual address. They need to advertise their individual IPs within the cluster.
Is cilium the only thing throwing errors here? It looks like cilium is trying to do a |
Thank you @brandond for taking the time to post a solution, this fixes the issues. New post-deployment configuration present on each server with
Last 50 lines of
|
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration: 3 servers, 5 agents
Describe the bug:
When I deploy the cluster, I use the following approach:
192.168.4.2
server deployment, I usecluster-init: true
192.168.4.3
,192.168.4.4
) withserver: 192.168.4.2
server: 192.168.4.10
server: 192.168.4.10
and restart the K3s serviceI'm encountering the following error into K3s logs, into each server:
Server configuration:
192.168.4.10
is the load balancer IP (see HAProxy configuration below)bind-address
Agent configuration:
HAProxy related configuration:
keepalived related configuration:
Additional context / logs:
K3s server logs in debug mode:
Cilium status:
The text was updated successfully, but these errors were encountered: