-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Poor error message when secrets-encryption only enabled on primary server #3220
Comments
Attaching the strace from our Slack conversation, in case its useful later:
|
This was fixed with #6409 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
K3s Version:
k3s version v1.20.6+k3s1 (8d04328)
go version go1.15.10
Node(s) CPU architecture, OS, and Version:
Linux k3s-500-2 5.4.0-72-generic #80-Ubuntu SMP Mon Apr 12 17:35:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
Bootstrapping High Availability with Embedded DB. Primary server configured; attempting to add second. Third server yet to be configured
Describe the bug:
The first server is bootstrapped and had
--secrets-encryption
enabled.When bootstrapping the second server,
--secrets-encryption
is omitted.The only log messages produced are:
Steps To Reproduce:
K3S_TOKEN=SECRET k3s server --cluster-init
--secrets-encryption`K3S_TOKEN=SECRET k3s server --server https://<ip or hostname of server1>:6443
(omit--secrets-encryption
)Expected behavior:
A more concise error message describing the failure. The HA docs should also indicate which options must be replicated on all server nodes
The text was updated successfully, but these errors were encountered: