Red Hat build of MicroShift

Provide external access to edge applications

Expose selected services on your MicroShift node to external clients in a controlled, secure, and observable way by using ingress controllers, routes, and router configuration.

Use ingress control in MicroShift
Configure ingress control in MicroShift
Ingress controller configuration fields in MicroShift
Create a secret for the ingress controller certificateSecret
Configure the TLS security profile for the ingress controller
About configuring the router
Router settings and valid values
Disable the router
Configure router ingress
Configure router ports
Configure router IP addresses
Configure the route admission policy
Create an HTTP-based route
HTTP Strict Transport Security
Enable HTTP Strict Transport Security per-route
Disable HTTP Strict Transport Security per-route
Enforce HTTP Strict Transport Security per-domain
Throughput issue troubleshooting methods
Use cookies to keep route statefulness
Annotate a route with a cookie
Path-based routes
HTTP header configuration
Set or delete HTTP request and response headers in a route
Create a route through an Ingress object
Create a route using the default certificate through an Ingress object
Create a route using the destination CA certificate in the Ingress annotation