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

with the current cluster-template only master shows up #99

Closed
gianarb opened this issue May 29, 2020 · 3 comments · Fixed by #101
Closed

with the current cluster-template only master shows up #99

gianarb opened this issue May 29, 2020 · 3 comments · Fixed by #101
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@gianarb
Copy link
Contributor

gianarb commented May 29, 2020

when #96 #98 will get merged you will notice that only the k8s master gets created, the workers do not for some reason.

we use DeploymentMachine for that, and I remember it worked a week ago, so probably something got lost along the way

@gianarb gianarb added the kind/bug Categorizes issue or PR as related to a bug. label May 29, 2020
@deitch
Copy link
Contributor

deitch commented May 31, 2020

I see it too. #98 is merged in, and #96, I just cheated by setting the PACKET_API_KEY to base64 encoded, so it all worked.

The master Machine came up, but nothing for the workers based on MachineDeployment.

Nothing in the packet manager logs either, which means it is not even calling them.

@deitch
Copy link
Contributor

deitch commented May 31, 2020

I think maybe I found your problem. PR coming soon

@deitch
Copy link
Contributor

deitch commented May 31, 2020

No, no PR needed. The default for WORKER_MACHINE_COUNT is 0. If you set it to something else, then it works. You can do it as an env var or as --worker-machine-count when calling clusterctl.

I will update the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants