Skip to content

Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Competitor MappingReference node

N/A (No port resource — server network interfaces managed implicitly via attach action)

Competitor mapping for Hetzner Cloud.

This page is a structured knowledge reference. For step-by-step migration guidance, see the migration guide.

Details

Provider
Hetzner Cloud
Service term
N/A (No port resource — server network interfaces managed implicitly via attach action)
Provider documentation
External reference

Behavioral divergences

N/A (No port resource — server network interfaces managed implicitly via attach action)

Quake AI concept: Ports

  • Hetzner has no port concept. Network attachment is managed at the server level via POST /v1/servers/{id}/actions/attach_to_network with an optional fixed IP. In Neutron, a port is an independent resource that can exist without a server attached, has its own UUID, security groups, and fixed IP.
  • Neutron ports support multiple fixed IPs per port, allowed-address-pairs for virtual IP failover (VRRP/keepalived), and port security disable. Hetzner network attachment has no equivalent of allowed-address-pairs or port security controls.
  • In Neutron, ports are the attachment point for security groups (POST /v2.0/ports with security_groups). Hetzner uses Firewalls (POST /v1/firewalls) attached to servers or server groups directly, not to network interfaces.
  • Neutron port status transitions (ACTIVE/DOWN/BUILD) are observable via API. Hetzner server network attachment status is an action result with no independent port lifecycle.

Related

Citations

  1. Hetzner Cloud
  2. Hetzner Cloud

These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.