Try to upgrade calico to 3.31 #524
Open
+10
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
cncf-cla: yes
zylxjtu
commented
Oct 31, 2025
| } | ||
|
|
||
| apply_workload_configuraiton(){ | ||
| log "wait for cluster to stabilize" |
zylxjtu
force-pushed
the
master
branch
2 times, most recently
from
848948f to
908e7cc
Compare
|
/retest |
msft-linliu
approved these changes
Nov 4, 2025
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: msft-linliu, zylxjtu 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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is based on #521, while we have met with issue for calico related pod on linux node.but the system pods such as calico-apiserver and calico-node pods are failing on linux node, while the calico-node* related pos are in running state on windows node. it looks hat during the installation of calico/cni, it will need to call DNS to reach to apiserver, while the coreDNS pod, without the cni being set up, will not be able to properly SNAT its request so it failed to request to upstream DNS.
the workaround here is to use ipaddress instead of the servername to calico-node to break this kind of deadlock.