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.

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

[BUG] How to use autok3s join new nodes when existed a cluster not created by autok3s #407

Closed
631068264 opened this issue Mar 16, 2022 · 9 comments
Assignees
Labels
bug Something isn't working to test Need to test
Milestone

Comments

@631068264
Copy link
Contributor

Describe the bug

I have a cluster created by k3s not autok3s, when I use autok3s to join a new node I get error

cluster xxxx is not exist

I read the code found that autok3s throw this because the autok3s.db in .autok3s dir

How to init this db ? It's impossible recreate a new cluster.

  • AutoK3s Version [e.g. v0.4.7]

Additional context
Add any other context about the problem here.

@631068264 631068264 added the bug Something isn't working label Mar 16, 2022
@Jason-ZW
Copy link
Collaborator

Starting from version v0.4.7 native provider does not support adding nodes to a cluster that is not managed by AutoK3s.

@Jason-ZW
Copy link
Collaborator

Jason-ZW commented Mar 17, 2022

The node addition function only supports clusters created by Autok3s, We'll try to find a way to support this scenario.

@631068264
Copy link
Contributor Author

Starting from version v0.4.7 native provider does not support adding nodes to a cluster that is not managed by AutoK3s.

I use older version autok3s to create cluster , use 0.4.7 join node also get same error

@Jason-ZW
Copy link
Collaborator

try v0.4.6?

@JacieChao
Copy link
Collaborator

We supported managing cluster lists handled by native provider in v0.4.7, but we don't save cluster information in the previous version. So the migration is not supported for now.
We will reconsider this situation in the next version.

@JacieChao JacieChao added this to the v0.4.9 milestone Mar 21, 2022
@JacieChao JacieChao assigned ly5156 and JacieChao and unassigned ly5156 Mar 23, 2022
@631068264
Copy link
Contributor Author

631068264 commented Mar 26, 2022

One more bug , when I create cluster failed , I can't recreate the cluster with the same name. I get error cluster xxx is already exist

@JacieChao
Copy link
Collaborator

@631068264 Could you please provide how to reproduce the problem?
I tried to create a cluster by native provider. If the cluster status is Failed, I can recreate the cluster with the same name no matter from UI (Back to Edit) or from CLI.

@631068264
Copy link
Contributor Author

Oh, I am very sorry. I made a mistake ,it occurred for a long time and suddenly remembered it yesterday . Create cluster success, and then use k3s_uninstall.sh to uninstall the cluster,when I recreate use the same name. I get the error.

I must del .autok3s dir when uninstall the cluster

@JacieChao
Copy link
Collaborator

fixed in v0.4.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working to test Need to test
Development

No branches or pull requests

4 participants