Slow and unreliable workspace connections when running Coder on multiple kubernetes clusters
Hi all, we have the current setup of:
cluster A: Running coder server
cluster B: Provisioning target for Coder Workspaces, configured as outlined in this document.
In this configuration, Workspaces provisioned on Cluster B are so slow to access over Coder that they are unusable. However, if we provision workspaces on the same cluster that the Coder server is running on (Cluster A), workspaces perform as expected.
Both cluster A and B share the same L2 network.
We also ran through forcing websocket connections following the tutorial here. as a debug step.
Is this a supported configuration? Are there any of debug steps/information we should look at for diagnose this issue? Any help would be greatly appreciated
cluster A: Running coder server
cluster B: Provisioning target for Coder Workspaces, configured as outlined in this document.
In this configuration, Workspaces provisioned on Cluster B are so slow to access over Coder that they are unusable. However, if we provision workspaces on the same cluster that the Coder server is running on (Cluster A), workspaces perform as expected.
Both cluster A and B share the same L2 network.
We also ran through forcing websocket connections following the tutorial here. as a debug step.
Is this a supported configuration? Are there any of debug steps/information we should look at for diagnose this issue? Any help would be greatly appreciated
