-
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
Split server setup fails on etcd-only, cp-only config #8672
Comments
Similar panic seen on 1.25 https://drone-pr.k3s.io/k3s-io/k3s/7616/3/3
|
Seeing the same thing with modules synced with upstream release/1.28 and using etcd-io/release-3.5 branch.
|
Initial testing using commit 6de9566 from dev branch
|
Validated using k3s version v1.28.3-rc1+k3s1 (6aef26e)Environment DetailsInfrastructure Node(s) CPU architecture, OS, and Version: Cluster Configuration: Config.yaml:
cp-only
Steps to reproduce the issue and validate the fix
Validation results:
|
Environmental Info:
K3s Version:
k3s version v1.28.2+k3s-b8dc9553
Node(s) CPU architecture, OS, and Version:
Ubuntu 22.04
Cluster Configuration:
1 etcd-only
1 cp-only
1 agent
Describe the bug:
After the etcd-only node is created, server-only node panics after few seconds of joining the cluster
Steps To Reproduce:
Expected behavior:
Cluster should be up with etcd-only and cp-only config and be able to join the agent
Actual behavior:
Seeing a panic on the logs after a while
Additional context / logs:
The text was updated successfully, but these errors were encountered: