-
Notifications
You must be signed in to change notification settings - Fork 2.3k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
k3s seems to ignore --data-dir option when rotating certs using script #7309
Comments
You shouldn't mix subcommands and flags, the CLI parser gets confused. Can you try I will also note that certificate rotation does not in general solve any problems. It is just a manual way to trigger something that will happen automatically when certs are about to expire. |
Hi, The
edit: thank you by the way for the additional note, will continue troubleshooting. |
This is quite interesting, I tried it again and now it worked. The exact same command.
I am still confused though as to why the option needs to be at the back of the command. |
That's not how you spell "certificate".
Flags go after commands. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Environmental Info:
K3s Version:
Node(s) CPU architecture, OS, and Version:
Linux macaw 5.10.0-21-arm64 #1 SMP Debian 5.10.162-1 (2023-01-21) aarch64 GNU/Linux
Cluster Configuration:
3 servers, 2 agents. All of them except one agent are
arm64
(one agent isamd64
).Describe the bug:
I am facing some TLS issues in the cluster and would like try rotating the certificates in the cluster. I tried to run
k3s -d /k3s certificate rotate
. With-d
as I have the k3s data on a seperate partition. I stopped k3s first. However it seems to ignore the option:One agent (the
amd64
one), is a slightly older version, but this issue was noticed on one of the server nodes.See also #7081.
Steps To Reproduce:
v1.26.3+k3s1 (01ea3ff2)
with data directory on a different location than default.k3s -d <dir> certificate rotate
.Expected behavior:
Certificates rotated succesfully.
Actual behavior:
An error was shown stating it cannot find the token.
Additional context / logs:
None.
Thank you! I hope I did not do something wrong and it actually does work. I did check this page and there does not seem to be test case covering this, but I am not sure if that is needed.
The text was updated successfully, but these errors were encountered: