Appearance
Services
Use a service when you want a stable internal address for a deployment.
In RemoteGPU, services are normal Kubernetes services inside your namespace. They are your resources, whether you create them from the console or with kubectl.
Open in the console
| Task | Console page |
|---|---|
| Create or inspect services | Kubernetes / Services |
Typical reasons to create a service
| Use case | Why a service helps |
|---|---|
| Internal app-to-app traffic | Gives other workloads a stable in-cluster target |
| Pod replacement and scaling | Keeps the target stable while pods restart or scale |
| Future public publishing | Provides the backend target for an ingress |
Supported service profile
| Area | Supported | Not supported |
|---|---|---|
| Service type | ClusterIP | NodePort |
| Public exposure model | Ingress backed by a service | externalIPs |
| Ownership model | Namespace-scoped Kubernetes Service | Platform-managed hidden service abstraction |
Choose a workflow
| Workflow | Best for | What happens |
|---|---|---|
Console | Guided setup for a deployment you already created | The console reads the deployment selector and creates a normal ClusterIP service |
kubectl | Full native control over the service manifest | You define the selector and ports directly |
Create a service
From the console:
- Open Kubernetes / Services
- Select a namespace
- Click
Create service - Choose the deployment you want to expose
- Provide the service details
| Console field | What it means |
|---|---|
Service name | Kubernetes service name in the namespace |
Service port | The port clients use to reach the service |
Target port | The container port or named target on the selected deployment |
The console reads the deployment selector and creates a normal ClusterIP service for that deployment.
After that, it behaves like any other Kubernetes service in the namespace.
Console and kubectl work on the same service list
The Services page shows the live services that currently exist in the namespace.
That includes services created from the console and services created with kubectl.
If you update or delete a service with kubectl, the console reflects that live state after refresh.
Next step: publish the service
If the service should be reachable from the internet, create an ingress for it.
An ingress points to one or more existing service backends and gives you HTTP routing for public access.