Ingress forwards HTTP or HTTPS requests to existing Services based on domain names and paths. Ingress does not directly associate with Pods; Services select the backend Pods, while Ingress is responsible only for configuring access routes.
Pre-Operation Confirmation
- A Service has been created to access backend Pods. For details, see Create and Manage a Service.
- The cluster has an installed component for processing Ingress routing.
Create Ingress
-
Log in to the GPU Cloud console and go to the Clusters page.
-
Click the name of the target cluster to access the cluster workspace.
-
In the left navigation pane, click Network.
-
Switch to the Ingress tab and click Create.
-
Configure Ingress.
Replace the domain name, Service name, and port with the actual values for your service. When preparing a complete Ingress manifest using Kubernetes YAML, you can refer to the following structure.
The service.name and port in the example must match those of the existing Service, and the Ingress and target Service must be in the same namespace.
-
Submit the creation. Return to the Ingress tab to verify that the Ingress has been created, and check whether the domain name, path, and target Service meet expectations.
Modify or Remove Access Entry Points
Modifying Ingress routes may change request forwarding behavior; deleting an Ingress will interrupt access that depends on this entry point. Before proceeding, confirm the domain name, path, target Service, and business impact.
-
On the Ingress tab, filter by namespace or use the search box to locate the target Ingress.
-
Perform actions as needed:
- Modify a route: Click Edit, make the changes, and submit them.
- Delete an entry: Click Delete, and verify the resource information in the confirmation dialog.