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

consider migrating away from Hetzner #70

Open
ldruschk opened this issue Jul 21, 2024 · 1 comment
Open

consider migrating away from Hetzner #70

ldruschk opened this issue Jul 21, 2024 · 1 comment
Labels
hetzner Hetzner-specific issues refactoring Improve/re-create existing features

Comments

@ldruschk
Copy link
Member

These issues caused us headaches:

  • blacklisted IPs (Dockerhub, golang packages, elastic.co etc.)
  • no more Servers of a given type available in a region (led to cursed Terraform files, where depending on the count.index servers need to be created in different regions)
  • Starting Servers from Snapshots takes ages, thus we had to start rhe Vulnboxes the evening before to guarantee all Vulnboxes are up in time, which leads to increased costs that might nullify the price difference when compared to othervproviders

Things to consider:

  • DigitalOcean is significantly more expensive (could be compensated with more sponsoring money, but this causes a dependency on sponsors even for smaller Bambi CTFs)
  • we would need to get sufficiently high limits in time before events
@ldruschk ldruschk added hetzner Hetzner-specific issues refactoring Improve/re-create existing features labels Jul 21, 2024
@ldruschk
Copy link
Member Author

Another one:

  • we occasionally had the issue that the whole API was unavailable (503), preventing us from starting/stopping servers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hetzner Hetzner-specific issues refactoring Improve/re-create existing features
Projects
Status: Ready
Development

No branches or pull requests

1 participant