Ingress with Service Mesh
FSM can optionally use the FSM ingress controller and Pipy-based edge proxies to route external traffic to the Service Mesh backend. This guide demonstrates how to configure HTTP ingress for services managed by the FSM service mesh.
Prerequisites
- Kubernetes cluster version v1.19.0 or higher.
- Interact with the API server using
kubectl
. - FSM CLI installed.
- FSM Ingress Controller installed followed by installation document
Demo
Assume that we have FSM installed under the fsm-system
namespace, and named with fsm
.
Save the external IP address and port of the entry gateway, which will be used later to test access to the backend application.
The next step is to deploy the sample httpbin
service.
Ensure that the httpbin
service and pod are up and running properly by
HTTP Ingress
Next, create the necessary HTTPProxy and IngressBackend configurations to allow external clients to access port 14001
of the httpbin
service under the httpbin
namespace. Because TLS is not used, the link from the fsm entry gateway to the httpbin
backend pod is not encrypted.
Now we expect external clients to have access to the httpbin
service, with the HOST
request header of the HTTP request being httpbin.org
.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.