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

k3s_control_token not working #187

Closed
niklasweimann opened this issue May 16, 2022 · 2 comments · Fixed by #190
Closed

k3s_control_token not working #187

niklasweimann opened this issue May 16, 2022 · 2 comments · Fixed by #190
Labels
bug Something isn't working

Comments

@niklasweimann
Copy link

Summary

When i set the k3s_control_token variable. The primary node initialises with a generated token and the secondary node tries to join the cluster with the token provided by k3s_control_token which obviously does not work.

Issue Type

  • Bug Report

Steps to Reproduce

Try to setup the k3s cluster with an external ha database.
Set the k3s_control_token with some value.
The primary node, which initializes the cluster will not use the token, but the secondary nodes will try to use the token.
=> Cluster can not be initialized.

k3s_cluster:
      vars:
        k3s_registration_address: 10.0.0.1
        k3s_control_token: <Some random string>

Expected Result

I expect the secondary Nodes to correctly join the cluster initialized by the primary node.

Actual Result

s. above
@niklasweimann niklasweimann mentioned this issue May 16, 2022
Merged
@niklasweimann
Copy link
Author

I have created a PR (#188) which fixed the behavior i described above. My cluster initialized successfully with this fix, so i think the fix should work fine, but please hit me up if i need to provide further information.

@crutonjohn
Copy link
Collaborator

Hey 👋🏻

Thanks for the PR, much appreciated. I approved the pipeline. The change seems benign enough to me.

@crutonjohn crutonjohn added the bug Something isn't working label May 20, 2022
@xanmanning xanmanning mentioned this issue May 29, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Niklasweimann main PyratLabs/ansible-role-k3s
2 participants
@niklasweimann @crutonjohn