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

Starting the router does not work if too many team configs are generated #36

Closed
Trolldemorted opened this issue Jun 15, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@Trolldemorted
Copy link
Member

for me it failed for 1024 iirc

@ldruschk ldruschk added the bug Something isn't working label Apr 5, 2024
@ldruschk
Copy link
Member

ldruschk commented Apr 5, 2024

Do you know where stuff went wrong? My first thoughts are this could be either because the config generation script generated config files with invalid IP addresses or because the user data included in terraform became too large

@ldruschk
Copy link
Member

ldruschk commented Jun 9, 2024

closing as duplicate of #45

@ldruschk ldruschk closed this as completed Jun 9, 2024
@Trolldemorted
Copy link
Member Author

hcloud has a strict upper length of cloudinit, and before configcleanup we had all generated team configs in cloudinit -> terraform apply failed if you have too many teams because you exceed the limit

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

No branches or pull requests

2 participants