Nish Anil

Thanks for the feedback, @cmargraff @robvet Can you validate this?

@riandesign hey! I haven't looked at that code in ages. Do you want to try a different layout and see if it works?

Thanks @eliassal These configuration will be part of the Environment variables that are set during deployment. These are configured in tye.yaml for local deployment. In Kubernetes, Tye uses Kubernetes secrets...

Hey @eliassal ! Thanks for pointing that out. For Zipkin, when prompted use `http://zipkin:9411` and for Redis use `redis:6379`.

Updated the docs. Let me know if it works now?

@eliassal When you apply the ServiceProfile configuration and refresh the page you won't see the error page again. This is because, the sidecar within the mesh is trying to retry...

What you see is an expected behavior - you don't see failures because we have handled that. In a microservices world, there are high chances for interim failures to occur....

Answering to your question on Grafana - One of the key features of a service mesh it to understand how the services are communicating with each other. Observability helps in...

Yes, the Polly code is not needed when using service mesh.