-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 server: relax ShardVirtualWorkspace flag validation #2659
🐛 server: relax ShardVirtualWorkspace flag validation #2659
Conversation
In kcp-dev#2407 we introduced this validation, but it doesn't handle the case where the VW server is not standalone, but you still want to specify --shard-virtual-workspace-url This scenario is likely when deploying a sharded environment, since you'll want the VW traffic to go via the front-proxy regardless of whether the VW server is standalone or not.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ncdc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test e2e-sharded Looks like #2654 |
/retest |
/retest Appears to be stuck in merge pool, not sure if retest will help but giving it a try... |
/refresh |
/test e2e-shared Raised #2665 to track the test failure, I can't reproduce locally so I'm assuming it's a flake |
Summary
In #2407 we introduced this validation, but it doesn't handle the case where the VW server is not standalone, but you still want to specify
--shard-virtual-workspace-url
This scenario is likely when deploying a sharded environment, since you'll want the VW traffic to go via the front-proxy regardless of whether the VW server is standalone or not.
Related issue(s)
Fixes an issue introduced via #2407