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
Currently, creating the RPC client at the driver initialization
might lead into an issue that, while upgrading to newer releases,
the RPC client will limit the maximum RPC version to the older
release's version, since that version is never refreshed while the
volume backend is running. Initializing the RPC client every time
it's needed will make sure it always refreshes the available
RPC service versions.
Also, inherit the RPC_DEFAULT_VERSION from the VolumeAPI, so that
the smallest available major version is requested by default,
instead of the biggest available version.
0 commit comments