Curated articles, resources, tips and trends from the DevOps World.
Summary: This is a summary of an article originally published by The New Stack. Read the full original article here →
The Istio service mesh comes with its own ingress, but we see customers with requirements to use a non-Istio ingress all the time. With some slight adjustments to the approach we suggested previously, we at Tetrate learned how to implement Traefik as the ingress gateway to your Istio Service Mesh.
In short, to get this to work in your own environment: The rest of this post covers deploying Istio’s Bookinfo sample application, using Traefik as the ingress proxy for the deployment.
Now it’s time to deploy Traefik by following v2.3 documentation (The most recent version of Traefik as of this post is 2.3, but it’ll work with any version of Traefik if you adjust the IngressRoute and Middleware resources as required for your version).
Logs are only available if the Istio install was done with the “meshConfig.accessLogFile=/dev/stdout” flag: This article demonstrates how Traefik Ingress can be implemented as an entry point to an Istio service mesh.
Made with pure grit © 2024 Jetpack Labs Inc. All rights reserved. www.jetpacklabs.com