kubernetes-sigs
Update calico version to 3.30.0 from 3.29.2
PR Description
Reason for Upgrading Calico from v3.29.2 to v3.30.0
We are upgrading Calico to version v3.30.0 to incorporate critical dependency updates and maintain compatibility with upstream container networking components.
Dependency Comparison
Calico Dependency Versions
| Dependency | Calico v3.29.2 | Calico v3.30.0 |
|---|---|---|
| Microsoft hcsshim | v0.11.8 |
v0.12.9 |
| Container Networking Plugins | ||
containernetworking/cni |
v1.2.0 |
v1.2.3 |
containernetworking/plugins |
v1.1.1 |
v1.6.2 |
Container Networking Plugins
| Dependency | master |
v1.7.1 |
v1.6.2 |
|---|---|---|---|
hcsshim |
v0.13.0 |
v0.12.9 |
v0.12.9 |
containernetworking/cni |
v1.3.0 |
v1.3.0 |
v1.2.3 |
:exclamation: Important Note
There have been changes in tiered policy naming changes introduced in Calico v3.29.4, which may impact policy definitions or enforcement in your current configuration. See Calico v3.29.4 Release Notes
Welcome @TinaMor!
It looks like this is your first PR to kubernetes-sigs/windows-testing 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-sigs/windows-testing has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @TinaMor. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: msft-linliu, TinaMor Once this PR has been reviewed and has the lgtm label, please assign adelina-t for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@TinaMor: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-e2e-capz-windows-2022-extension | 338e08d483d03486a4f8a51bcefa8ab8f9fd025a | link | false | /test pull-e2e-capz-windows-2022-extension |
| pull-e2e-capz-windows-2025-extension | 338e08d483d03486a4f8a51bcefa8ab8f9fd025a | link | false | /test pull-e2e-capz-windows-2025-extension |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
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. I understand the commands that are listed here.
It looks like the nodes came up but never got CNI running
Thu, 26 Jun 2025 17:37:21 +0000: cleaning up
./capz/run-capz-e2e.sh: line 104: capz::ci-build-azure-ccm::cleanup: command not found
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
capz-conf-31cjab-control-plane-pxp5k NotReady control-plane 5m26s v1.34.0-alpha.2.45+00d375050338df <none> <none> Ubuntu 24.04.2 LTS 6.8.0-1021-azure containerd://1.7.20
capz-conf-gzmpj NotReady <none> 3m3s v1.34.0-alpha.2.45+00d375050338df <none> <none> Windows Server 2022 Datacenter 10.0.20348.3328 containerd://1.7.20
capz-conf-qs6w5 NotReady <none> 3m20s v1.34.0-alpha.2.45+00d375050338df <none> <none> Windows Server 2022 Datacenter 10.0.20348.3328 containerd://1.7.24
Thu, 26 Jun 2025 17:37:21 +0000: collecting logs
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
