Open praveensanap opened 1 year ago
We horizontally scale our backstage backend servers on k8s.
grpc-playground works in two steps.
/proto-info/:entity
/send-request/:entity
now if there are two pods backstage backend, first call can go to first pod, and second call can go to second pods, and cause missing proto error.
Is there a way to solve this by having a common source for .proto files, say like GCS/S3 bucket.
Thanks. This plugin should support backstage discovery feature
Please try configuring AWS S3 discovery along with this configuration guideline and report if it works
We horizontally scale our backstage backend servers on k8s.
grpc-playground works in two steps.
/proto-info/:entity
endpoint. where the proto definition is copied to local file./send-request/:entity
where the actual call is made.now if there are two pods backstage backend, first call can go to first pod, and second call can go to second pods, and cause missing proto error.
Is there a way to solve this by having a common source for .proto files, say like GCS/S3 bucket.