So, we want to add the 'cluster' attribute t ovolumes in an upgrade safe manner
Pre-upgrade we are on some RPC version, I'm going to call 1.12 for no good reason
The new release finishes with real RPCs at 1.25
So, if we do a rolling upgrade, then the RPC version number will stay below 1.25 until we know everybody is running the new code. If we make the create RPC that fills in the version field RPC version 1.26, then make sure API never calls it until the minimum supported RPC version anyeverywhere is 1.26, then we should be safe for that RPC version to start filling in the cluster field.