Ingresses

Use an ingress when you want HTTP traffic from outside the cluster to reach a service in your namespace.

RemoteGPU supports Kubernetes Ingress for professional Kubernetes users. The console can help you create a simple ingress, and kubectl can manage the same resource directly.

Open in the console

Task	Console page
Create or inspect ingresses	Kubernetes / Ingresses

Before you create an ingress

Requirement	Why it matters
A running workload	Ingress only routes traffic; it does not run the application
A ClusterIP service	Ingress backends must point to an existing service
A supported host under apps.remotegpu.ai	Hosts outside the managed ingress domain are rejected
The platform ingress class	The current supported class is nginx

Choose a workflow

Workflow	Best for	What happens
Console	Guided ingress creation for an existing service	You choose the service, port, host, and path in the UI
kubectl	Full native control over the Kubernetes ingress manifest	You create a networking.k8s.io/v1 Ingress directly

Supported ingress profile

Area	Supported behavior
API version	networking.k8s.io/v1 Ingress
Backend type	Service-backed HTTP rules
Namespace boundary	The ingress must point to services in the same namespace
Hostnames	Hosts under the RemoteGPU-managed ingress domain
Ingress class	The platform ingress class, currently nginx
Path routing	Standard HTTP path routing with pathType

In practice, the supported flow is:

Deployment
  -> Service
  -> Ingress
  -> public HTTP route

Unsupported ingress patterns

Pattern	Current status
NodePort or externalIPs service exposure	Not supported
Hosts outside the managed ingress domain	Not supported
defaultBackend	Not supported
Non-service ingress backends	Not supported
Unsupported ingress-controller annotations	Not supported
Custom-domain onboarding through the Kubernetes console flow	Not supported

Create an ingress

From the console:

1. Open Kubernetes / Ingresses
2. Select a namespace
3. Click Create ingress
4. Choose the target service
5. Choose the backend port
6. Enter the ingress details

Console field	What it means
Ingress name	Kubernetes ingress name in the namespace
Host	Public host under apps.remotegpu.ai
Path	HTTP path for the backend rule
Service	Existing service that should receive traffic
Port	Service port the ingress backend should target

The console creates a Kubernetes ingress that points to the existing service.

How ingress shows up in the console

The console reads live ingress resources from your namespace.

Action	Result
Create ingress with kubectl	It appears in the console
Create ingress in the console	It appears in kubectl
Remove the target service or service port	The console shows an error state for the ingress

Read next

• Read Services if you still need the internal backend.
• Read Deployments if the workload is not running yet.