tldr - powered by Generative AI

• The solution involves using a lookup service to extract the ID to route the chart or throughout the request
• The routing policy creates an HTTP sidecar outbound filter on the clients
• The solution provides flexibility for service owners to define the config they want to use and the lookup service to be used
• The solution was pre-built with the Envoy proxy and the Vasan binary was copied into the image and referenced in the Envoy filter
• Config Maps in Kubernetes have a limit of 100 MB and may not be able to store binaries larger than that