Ingress Controller

An ingress controller is used to expose your application endpoints outside your Kubernetes cluster. Ingress Controller resource represents Ingress Controller configuration.

You must do the configurations mentioned in Exposing Apps with Ingress Controller topic to expose BW6 (Containers) and Flogo apps using Ingress Controller.

Property Description
Ingress Controller

Specify type of ingress controller:

  • NGINX

  • Kong (Kong ingress controller is supported for BusinessWorks Container Edition and TIBCO Flogo app endpoints only)

  • Traefik

  • OpenShift Router: Use this for OpenShift data plane
Resource name

Name of the resource
Ingress Class name

The Ingress class name used in the Ingress specification.

Example: nginx
FQDN

Fully qualified domain name (FQDN) configured for Ingress Controller.

Note: You must use a unique FQDN and path prefix combination within a single cluster for the same ingress controller resource.
Ingress Annotations This option enables you to pass custom annotations to Ingress Controller. Custom annotations allow you to customize behavior of Ingress Controller according to your needs.
Key

Key of annotation

Example: nginx.org/proxy-connect-timeout
Value

Value of annotation

Example: 30s
Note: You can change the ingress controller resource when updating configuration for a capability.

Ingress Definition for Routers

To avoid conflicts and ensure correct request handling, ingress definitions must be fully qualified. This means you specify each subdomain explicitly in your ingress rules rather than using wildcards.

For example, instead of using *.customer.com, define separate ingress rules for each required subdomain:

  • admin.customer.com

  • cp1.customer.com

  • cp2.customer.com

This practice ensures that the router routes requests only to their intended destinations, preventing inadvertent processing of unrelated subdomains.