Hi all! Apologies for probably bungling some of th...
# ask-community
j
Hi all! Apologies for probably bungling some of the terminology here. My team is looking at a deployment architecture where we have one dagster instance, and individual remote GRPC hosts for each of our pipeline projects. I’m wondering if there is any guidance about how far apart dagster versions can be between a dagster instance and GRPC host that the instance is communicating with. Maybe the answer is in this really helpful doc on Releases and Compatibility that states core APIs won’t have breaking changes within a major version, so all of the GRPC hosts need to be on the same major version as the dagster instance, but I’m just not that confident in my reading of the doc.
👀 1
🤖 1
s
Yes, gRPC code servers just need to be on the same major version: so 1.x. We try hard to maintain compatibility-- Dagster Cloud gets updated to the latest version every week, and if we didn’t our customers would constantly need to upgrade their pipeline code!