---
schema_version: "1"
id: f55c3cab3f8db544b7b692f7c242fa47a36b0f8597200648f3073233e2a8c649
title: Configuring Ingress Endpoints for Mule App Deployment
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-fabric/2.9/configure-ingress-endpoints.md
canonical_url: https://docs.mulesoft.com/runtime-fabric/2.9/configure-ingress-endpoints
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 02cde3bdd26f31dd9dd8b1d786f8826b35d0cd52e8ef2fca94263dad62754156
description: MuleSoft Documentation Site
release: "2.9"
latest: false
---
---
product: Runtime Fabric
version: 2.9
---

# Configuring Ingress Endpoints for Mule App Deployment

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To configure ingress endpoints for a Mule app deployment, complete these tasks:

1.  Create an ingress resource template and apply it in the cluster.

2.  Configure ingress for a Mule app.

## Before You Begin

Before configuring ingress in Runtime Fabric, set up an ingress controller. For a list of ingress
controllers, refer to the
[Kubernetes documentation](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/).

## Create an Ingress Resource Template and Apply it in the Cluster

Use one of the [example templates](https://docs.mulesoft.com/runtime-fabric/2.9/custom-ingress-configuration#kubernetes-ingress) to create an
ingress resource.

1.  Copy the example template into a new file and modify it according to the notes.

2.  Include a `.yaml` extension in the file name.

3.  To apply an ingress template, run:

    ```copy
    kubectl apply -f <TEMPLATE_FILENAME.yaml>
    ```

If there is an issue in the template, Kubernetes `api-server` returns an error and the command
fails.

After you apply a template successfully, you can view it with:

```copy
kubectl describe ingress [Ingress Name] -n rtf
```

## Configure Ingress for a Mule App

You configure ingress for an application when you deploy it to Runtime Fabric using Runtime Manager.
Available hosts and paths for an application come from the ingress resource template configured by
the Runtime Fabric administrator.

You can also use this procedure to deploy a test application to validate your ingress resource
template.

> [!NOTE] The following provides an overview of how to configure ingress for an application. Refer
> to [Deploy a Mule Application to Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/2.9/deploy-to-runtime-fabric) for complete deployment
> instructions. If you are using the Mule Maven plugin to deploy applications to Runtime Fabric, the
> deployment settings parameter `publicUrl` in the block `http` can accept a comma-delimited string
> of multiple endpoints. For more information, see
> [deploymentSettings Parameters Reference](https://docs.mulesoft.com/mule-runtime/latest/deploy-to-rtf#deploymentsettings-parameters-reference).

1.  Navigate to Runtime Manager and follow the documentation to deploy an application to Runtime
    Fabric.

2.  Select **Ingress**.

3.  From the **Host** drop-down list, select a host for the application.

4.  If the hostname uses a wildcard, add a subdomain in the **Subdomain** field.

    The **Subdomain** field is only available if the hostname uses a wildcard.

5.  In the **Path** field, add a URL path to the application’s endpoint:

    ![The host and path fields are populated for the endpoint](/mulesoft/current/en-us/runtime-fabric/2.9/_images/rtf-ingress-endpoint.png)

6.  To preview the endpoint, click the generated preview link.

7.  To add additional endpoints, click **\+ Add Endpoint**.

8.  When ready, click **Deploy application**.

## See Also

- [Configure Ingress in Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/2.9/configure-ingress)