Network Interfaces

Network interfaces let an existing virtual machine join additional networks after the original order is already running. This is useful when a single VM must handle both public and private traffic, or when you need to attach a new service path without rebuilding the machine.

What an interface does

• Binds one VM to one selected virtual network.
• Can expose a public path when attached to a Bridge network.
• Can extend private connectivity when attached to a NAT network.

Create an interface

1. Open the virtual machine details page.
2. Go to the Interface section.
3. Click Create Interface.
4. Enter the interface name and optional description.
5. Select the target virtual network.
6. If the selected network is a Bridge network, select a security group.
7. Confirm the order or creation request.

Important behavior in RESVRL

• NAT interfaces can be created directly without an extra public-access order step.
• Bridge interfaces may require an order flow because they consume public network resources.
• Security-group selection is required when the interface includes public connectivity.

Typical use cases

Add a private backend path

Attach a NAT interface when the VM needs to reach internal services, databases, or a Kubernetes private network.

Add a public entry path

Attach a Bridge interface when the workload needs an additional public IP or needs to be moved onto a separate public network policy.

Separate service traffic from management traffic

Use one interface for user-facing traffic and another for administration or internal service calls.

Before adding a public interface

• Confirm that the target Bridge network is correct.
• Prepare a security group with the minimum required rules.
• Check the expected cost if the order drawer shows public network pricing.

Before deleting an interface

• Make sure the VM still has a reachable management path.
• Check whether application routes or firewall rules depend on the interface.
• Remove or update any services bound to the interface IP.