Skip ExternalTrafficPolicy short-circuit test in cloud-provider-azure multi-zone-vmss-capz job#36957
Conversation
… multi-zone-vmss-capz job Signed-off-by: William Yao <william2000yao@gmail.com>
|
/assign @nilo19 |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx, willie-yao The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@willie-yao: Updated the
DetailsIn response to this:
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-sigs/prow repository. |
The
cloud-provider-azure-conformance-multi-zone-vmss-capzjob is failing on[sig-network] Services should implement NodePort and HealthCheckNodePort correctly when ExternalTrafficPolicy changes.The test asserts that source IP is preserved through kube-proxy's
externalTrafficPolicy=Localshort-circuit path, which is incompatible withCAPZ's default Calico VXLAN encapsulation (the source IP gets rewritten to the
node's
vxlan.calicotunnel address).Only this job is affected because it uses
WORKER_MACHINE_COUNT: "3"; the testrequires ≥3 schedulable workers and is skipped automatically elsewhere.
Refs: kubernetes-sigs/cloud-provider-azure#9863, kubernetes-sigs/cluster-api-provider-azure#6252