[Feature]: Ability to create a new server attached to a private subnet without having to manually manage the IP

[mzhaase]

What whould you like to see?

Creating a server that is reachable only via a private subnet is an extremely common use case - maybe the most common use case.

Currently, this is not possible by only using terraform at scale. One has to implement their own IPAM solution to assign IP addresses at creation time. This is not really sensible, when talking about hundreds of servers, managed by multiple independent teams.

Ideally, something similar to this would be implemented.

resource "hcloud_server" "this" {
    [...]
    public_net {
        ipv4_enabled = "false"
        ipv6_enabled = "false"
    }
    subnet_id = hcloud_subnet.this.subnet_id
}

The server would then be created, with its primary IP chosen randomly from one of the available IPs in hcloud_subnet.this.

As part of this it would also be great for subnets to have labels so we could use a data source to get the subnet_id.

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.

[apricote]

Hey @mzhaase,

you said:

The server would then be created, with its primary IP chosen randomly from one of the available IPs in hcloud_subnet.this.

This does not work, subnets belong to a (private) Network, and they do not contain publicly routable Primary IPs.

If you meant to assign private IP from the subnet, please see #672 for an explanation of the issue. Closing this as duplicate.