> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scitix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Expose Cluster Services Using Ingress

> Configure HTTP or HTTPS routes for existing Services, review request forwarding relationships, and maintain Ingress.

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](https://docs.scitix.ai/gpu-cloud/cluster/create-and-manage-service.md).
* The cluster has an installed component for processing Ingress routing.

## Create Ingress

1. Log in to the [GPU Cloud console](https://console.scitix.ai/gpu-cloud/home) and go to the **Clusters** page.

2. Click the name of the target cluster to access the cluster workspace.

3. In the left navigation pane, click **Network**.

4. Switch to the **Ingress** tab and click **Create**.

5. Configure Ingress.

   | Parameter | Description |
   | - | - |
   | **Name** | Set the Ingress name. We recommend using a name that reflects the purpose of the service or entry point. |
   | **Namespace** | Select the namespace to which the Ingress belongs. An Ingress must reference Services in the same namespace. |
   | **Labels** | Optional. Add labels to identify or filter the Ingress. |
   | **Spec (YAML)** | Enter the Kubernetes spec for the Ingress. Include only the content under `spec`; `apiVersion`, `kind`, and `metadata` are not required. |

   **Ingress Spec Example**

   Replace the domain name, Service name, and port with the actual values for your service.

   ```yaml theme={null}
   rules:
     - host: example.com
       http:
         paths:
           - path: /
             pathType: Prefix
             backend:
               service:
                 name: nginx-service
                 port:
                   number: 80
   ```

   **Complete Ingress YAML Reference**

   When preparing a complete Ingress manifest using Kubernetes YAML, you can refer to the following structure.

   ```yaml theme={null}
   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     name: nginx-ingress
     namespace: default
   spec:
     rules:
       - host: example.com
         http:
           paths:
             - path: /
               pathType: Prefix
               backend:
                 service:
                   name: nginx-service
                   port:
                     number: 80
   ```

   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.

6. 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

> [!WARNING]
>
> 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.

1. On the **Ingress** tab, filter by namespace or use the search box to locate the target Ingress.

2. 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.