Connect a private datacenter

A private datacenter is a location you operate. After you install the Maxoperf agent inside your network, tests can pick that location and generate load from there. Use it for internal services, regulated environments, or any system that should not be reachable from the public internet.

The install path is the same for a single Docker host and for a Kubernetes cluster.

Before you start

You need:

• A workspace where you can create a private datacenter.
• A Docker host or a Kubernetes cluster inside the network that can reach the target.
• Outbound HTTPS connectivity from that host to the Maxoperf service endpoints.

Register the datacenter

1. Open the workspace and switch to the Private datacenters tab.

   

   The Private datacenters list shows every PDC the workspace owns, with its status.

2. Click New private datacenter.

3. Give it a clear name, like aws-us-east-internal or colo-rack-3 and a short description.

4. Pick the runtime: Docker for a single host or Kubernetes for a cluster.

5. Save. Maxoperf generates a one-time enrollment token and an install snippet.

Install the agent

1. Copy the install snippet from the console. It includes the enrollment token and the public service endpoints the agent needs to reach.

2. Run the snippet on the host or cluster you chose. The agent registers with Maxoperf using the one-time token, then exchanges it for a long-lived identity.

3. Watch the agent status on the private-datacenter page in the console. The status moves from pending enrollment to running when the agent connects.

   

   On the Private datacenter detail page, the meta pill row shows the current agent status. Auto-update readiness and identity sit below it.

Treat the enrollment token like a secret

The enrollment token is single-use and short-lived. Until it expires, anyone who has it can register an agent against your workspace. Do not paste it into shared chat channels or commit it to a repository.

Use the location in a test

When the agent shows running, the location appears in the Locations dropdown as you create or edit a test. Pick it like any other location.

You can mix this location with managed cloud locations in the same test. For example, run 80% of the load from a managed region and 20% from your private location to compare.

Operate the agent

• Upgrade: the agent upgrades itself on a controlled schedule. To pin a specific version, opt out per agent.
• Pause: when you disable the location, MaxoPerf schedules no new runs to it. Runs in progress continue to completion.
• Revoke: deleting the private datacenter removes the agent’s identity. To bring it back, you enroll it again.

Where to go next

• Managed and private load locations: when each kind of location fits.
• Use case: private load generation: patterns from teams that run production traffic from their own infrastructure.
• Run your first test: pick the new location when you create the test.