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.

Sign up for GitHub

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

Jump to bottom

[Release-1.31] - Secondary etcd-only nodes do not reconnect to apiserver after outage if joined against an etcd-only node #11320

Open

brandond opened this issue Nov 14, 2024 · 0 comments

Assignees

Milestone

Member

brandond commented Nov 14, 2024

Backport fix for Secondary etcd-only nodes do not reconnect to apiserver after outage if joined against an etcd-only node

Secondary etcd-only nodes do not reconnect to apiserver after outage if joined against an etcd-only node #11311

brandond self-assigned this

github-project-automation bot added this to K3s Development

github-project-automation bot moved this to New in K3s Development

brandond mentioned this issue

[release-1.31] Fix issue with loadbalancer failover to default server #11324

Merged

caroline-suse-rancher moved this from New to Peer Review in K3s Development

caroline-suse-rancher added this to the v1.31.3+k3s1 milestone

mdrahman-suse assigned aganesh-suse

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment