You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Service resolvers added to a tagged service with multiple instances (different tags) is not completely shown in the (routing) UI of the service.
Reproduction Steps
End goal is to be able to connect from a Nomad Job to a specifically tagged instance of the service (i,e the primary - see steps to reproduce)
Steps to reproduce this issue:
Have a service with multiple instances, each instance tagged with a different tag.
In this case, we have a patroni cluster consisting of (at least) 2 instances, one instances tagged as primary the other tagged as replica - service name is postgres-16.
Overview of the Issue
Service resolvers added to a tagged service with multiple instances (different tags) is not completely shown in the (routing) UI of the service.
Reproduction Steps
End goal is to be able to connect from a Nomad Job to a specifically tagged instance of the service (i,e the primary - see steps to reproduce)
Steps to reproduce this issue:
In this case, we have a patroni cluster consisting of (at least) 2 instances, one instances tagged as primary the other tagged as replica - service name is
postgres-16
.Based on these example: https://discuss.hashicorp.com/t/how-to-reach-a-service-subset-from-the-service-mesh/45162/2
create 2 service resolvers:
(shows the main resolver and the default subset)
Trying to access the services from a Nomad Job, works only for the main
postgres-16
service but not the tagged/filtered services:The text was updated successfully, but these errors were encountered: