Skip to content

Service mesh Ingress configuration

Service mesh Ingress configuration involves defining rules for managing external traffic entry into the mesh, typically utilizing resources like Gateway and VirtualService.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__websockets__README.md]

Gateway and VirtualService

To control Ingress, specific configuration resources are created to enable routing and protocol upgrades.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__websockets__README.md] For example, a VirtualService can be configured to support WebSocket upgrades for incoming traffic^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__websockets__README.md].

[kubectl](<./kubectl.md>) create -f samples/websockets/route.yaml
^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__websockets__README.md]

Ingress IP and Ports

After configuration, determining the specific entry point is necessary for external access.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__websockets__README.md] This requires identifying the Ingress gateway IP and associated ports.^[400-devops__07-Monitoring-and-Observability__k8s-istio__samples__websockets__README.md]

Sources

  • 400-devops__07-Monitoring-and-Observability__k8s-istio__samples__websockets__README.md