Description

Ensure Public Cloud projects that run production workloads are attached to a vRack, OVHcloud's private network, so that instances, databases, Kubernetes clusters, and other services can communicate over private networks instead of the public internet.

Rationale

Without a vRack, services must talk to each other over public IP addresses, which exposes them to the internet and requires more firewall rules. The vRack allows private networks that keep internal traffic isolated, reduces the attack surface, and is required for private networking on many managed services.

Impact

  • Internal traffic stays on private networks

  • Reduces public exposure of services

  • Required for private networks on managed services

Default Value

A vRack is not attached by default; it is created or attached when you first set up a private network.

Pre-Requisites

  • Permission to manage the Public Cloud project

Test Plan

  1. Log in to the OVHcloud Control Panel at https://www.ovh.com/manager/.

  2. In the left-hand menu, select Public Cloud and choose your project.

  3. In the left-hand menu, under Network, select Private Network.

  4. Verify that a vRack is active for the project (it also appears in the Control Panel under Network > vRack private network, labelled pn-xxxxxx).

  5. If no vRack is attached, follow the implementation steps.

Implementation Steps

  1. Log in to the OVHcloud Control Panel at https://www.ovh.com/manager/.

  2. In the left-hand menu, select Public Cloud and choose your project.

  3. In the left-hand menu, under Network, select Private Network and follow the prompt to activate a vRack for the project.

  4. Once the vRack is active, create the private networks and subnets you need from the same page.

Backout Plan

  1. Log in to the OVHcloud Control Panel at https://www.ovh.com/manager/.

  2. In the left-hand menu, select Public Cloud and choose your project.

  3. Remove the private networks that are no longer needed, then detach the project from the vRack.

Reference