Deployments

Use a deployment when you want to run an application in a namespace.

Choose a workflow

Workflow	Best for	What RemoteGPU expects
Console	Guided setup and quick edits	You choose the deployment fields in the UI
kubectl	Git-managed manifests and CI	Your deployment must include the right labels and pass admission checks

What a deployment controls

Field area	Purpose
Image	Which container image to run
Replicas	How many copies should stay running
Plan	Which RemoteGPU compute SKU to use
Container port	Which application port later services may target
Probes and environment	Optional runtime settings for health and configuration

A deployment does not make your application reachable by itself. To send traffic to it, create a service. To make that service public, create an ingress.

Before you create a deployment

Check	Why it matters
Choose a namespace first	Deployments are namespace-scoped
Decide whether the workload needs internal or public traffic	That determines whether you also need a Service or Ingress
Pick a plan that matches the workload	The selected SKU controls scheduling and resource defaults

Create a deployment

From the console:

1. Open Kubernetes / Deployments
2. Select a namespace
3. Click Create deployment
4. Fill in the deployment form

Console field	What it means
Deployment name	Kubernetes deployment name in the selected namespace
Image	The container image to run
Replica count	How many pods the deployment should keep running
Plan	The RemoteGPU SKU for scheduling and defaults
Container port	The application port that later services may target

The container port is only a hint for the runtime and later service creation. It does not create a public URL.

Choosing a plan

The plan you pick in the console maps to a RemoteGPU SKU.

If you work in the console, the plan picker handles this for you.

If you work with kubectl, add the SKU label to the deployment pod template:

metadata:
  labels:
    remotegpu.ai/sku-code: gpu-h100-1x

If the SKU label is missing or conflicts with the requested resources, the deployment will not be admitted.

Console and kubectl operate on the same deployment

Action	Result
Create in the console	The deployment appears in kubectl
Apply with kubectl	The deployment appears in the console
Update or scale in either place	The other view reflects the live deployment state

After the deployment is running

Most applications need one or both of these next steps:

1. Create a service so traffic inside the namespace can reach the deployment.
2. Create an ingress if you want public HTTP access.

Read next

• Read Services to expose the deployment inside the cluster.
• Read Ingresses when you need public HTTP access.