[WIP] 🐛 sharded-test-server: Add external-hostname flag #2672
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@ncdc I think this reproduces the issues seen in "real" cluster deployments, because we're using the ExternalAddress for the vwURL since #2407 - I tried to work around that in #2667 How is controller sharding handled? I assume we can't just use |
hardys
force-pushed
the
sharded_bootstrap_fixes
branch
from
3f15ee5 to
599df20
Compare
We are seeing real cluster deployments of KCP fail because the external-hostname and shard-external-url flags typically point to the front-proxy endpoint, this aligns the e2e behavior so we can work through the issues with chicken/egg availability during shard bootstrapping.
hardys
force-pushed
the
sharded_bootstrap_fixes
branch
from
599df20 to
2a5795a
Compare
|
@hardys: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
@hardys I think I missed your question above somehow. Wanted to follow up and see if we still want this PR? If so, how can I help? |
Summary
We are seeing real cluster deployments of KCP fail because the external-hostname and shard-external-url flags typically point to the front-proxy endpoint, this aligns the e2e behavior so we can work through the issues with chicken/egg availability during shard bootstrapping and discuss the best solution.