-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Support the creation of servers with only private networks #129
Comments
Due to #130 I haven't been able to do the change directly in the code (because the Taking the official I added in component.js the
And then I also changed the
If anyone likes the change I have no issues raising a PR, but the current github code doesn't generate a valid |
Recently Hetzner has added the support of servers belonging only to private networks, without any public interface, thank to the following options:
This is a great achievement for security and architectural purposes, and the driver https://github.com/JonasProgrammer/docker-machine-driver-hetzner has implemented the support for this in version 3.8.0 (see this issue for more information).
It would be great if we supported this from the UI driver too.
In order to implement this we should offer a new option called
disable-public
(includes both ipv4 & ipv6), only applicable when at least one private network is selected. This option would use the new flag implemented in the driver, called--hetzner-disable-public
.The usage of
--hetzner-disable-public
should also imply the usage of--hetzner-use-private-network
and the association of at least one private network to the server.Another option would be to include 2 extra
checkboxes
todisablePublic4
anddisablePublic6
independently (associated with machine driver parameters--hetzner-disable-public-4
and--hetzner-disable-public-6
.The text was updated successfully, but these errors were encountered: