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.

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.28] - Secondary etcd-only nodes do not reconnect to apiserver after outage if joined against an etcd-only node #11323

Open
brandond opened this issue Nov 14, 2024 · 0 comments
Open

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

brandond opened this issue Nov 14, 2024 · 0 comments
Assignees
@brandond @aganesh-suse
Milestone
v1.28.16+k3s1

Comments

@brandond
Copy link
Member

Backport fix for Secondary etcd-only nodes do not reconnect to apiserver after outage if joined against an etcd-only node
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brandond brandond

@aganesh-suse aganesh-suse

Labels
None yet
Projects
K3s Development
Status: To Test
Milestone
v1.28.16+k3s1
Development

No branches or pull requests
3 participants
@brandond @caroline-suse-rancher @aganesh-suse