Skip to content

feat: implemented fallback mechanism for when CNI does not provide an… #554

feat: implemented fallback mechanism for when CNI does not provide an…

feat: implemented fallback mechanism for when CNI does not provide an… #554

Triggered via pull request June 5, 2026 22:12
Status Failure
Total duration 2m 50s
Artifacts

govulncheck.yaml

on: pull_request
Check all go.mod files are in matrix
4s
Check all go.mod files are in matrix
Matrix: govulncheck
Fit to window
Zoom out
Zoom in

Annotations

37 errors and 38 warnings
Run govulncheck (tools/azure-npm-to-cilium-validator)
Process completed with exit code 3.
Run govulncheck (tools/azure-npm-to-cilium-validator)
azure.main calls core.pods.List, which eventually calls http2.unencryptedTransport.RoundTrip
Run govulncheck (tools/azure-npm-to-cilium-validator)
azure.main calls core.pods.List, which eventually calls http2.noDialH2RoundTripper.RoundTrip
Run govulncheck (tools/azure-npm-to-cilium-validator)
azure.main calls core.pods.List, which eventually calls http2.noDialH2RoundTripper.NewClientConn
Run govulncheck (tools/azure-npm-to-cilium-validator)
azure.main calls core.pods.List, which eventually calls http2.Transport.RoundTrip
Run govulncheck (tools/azure-npm-to-cilium-validator)
azure.main calls core.pods.List, which eventually calls http2.Transport.NewClientConn
Run govulncheck (tools/azure-npm-to-cilium-validator)
azure.main calls core.pods.List, which eventually calls idna.ToASCII
Run govulncheck (azure-ipam)
Process completed with exit code 3.
Run govulncheck (azure-ipam)
azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.unencryptedTransport.RoundTrip
Run govulncheck (azure-ipam)
azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.noDialH2RoundTripper.RoundTrip
Run govulncheck (azure-ipam)
azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.noDialH2RoundTripper.NewClientConn
Run govulncheck (azure-ipam)
azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.Transport.RoundTrip
Run govulncheck (azure-ipam)
azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.Transport.NewClientConn
Run govulncheck (azure-ipam)
azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls idna.ToASCII
Run govulncheck (azure-iptables-monitor)
Process completed with exit code 3.
Run govulncheck (azure-iptables-monitor)
azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls http2.unencryptedTransport.RoundTrip
Run govulncheck (azure-iptables-monitor)
azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls http2.noDialH2RoundTripper.RoundTrip
Run govulncheck (azure-iptables-monitor)
azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls http2.Transport.RoundTrip
Run govulncheck (azure-iptables-monitor)
azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls http2.Transport.NewClientConn
Run govulncheck (azure-iptables-monitor)
azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls idna.ToASCII
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (azure-iptables-monitor)
Cannot open: File exists
Run govulncheck (.)
Process completed with exit code 3.
Run govulncheck (.)
internal.WireserverTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls http2.unencryptedTransport.RoundTrip
Run govulncheck (.)
internal.WireserverTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls http2.noDialH2RoundTripper.RoundTrip
Run govulncheck (.)
internal.WireserverTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls http2.noDialH2RoundTripper.NewClientConn
Run govulncheck (.)
internal.WireserverTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls http2.Transport.RoundTrip
Run govulncheck (.)
internal.WireserverTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls http2.Transport.NewClientConn
Run govulncheck (.)
internal.WireserverTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls idna.ToASCII
Run govulncheck (zapai)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (zapai)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0NUojagAAAADP71rrxvYIQ6atNY5BPeD4UEhMMzBFREdFMDQxOQBFZGdl
Run govulncheck (zapai)
Failed to restore: Cache service responded with 400
Run govulncheck (zapai)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (dropgz)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (dropgz)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0OEojagAAAACDYqwAY8riRLcztz6mNrmHUEhMMzBFREdFMDQwOABFZGdl
Run govulncheck (dropgz)
Failed to restore: Cache service responded with 400
Run govulncheck (dropgz)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (pkgerrlint)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (pkgerrlint)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0OUojagAAAAB6QHdV8cjsRo1m98dDIAkRUEhMMzBFREdFMDIwNwBFZGdl
Run govulncheck (pkgerrlint)
Failed to restore: Cache service responded with 400
Run govulncheck (pkgerrlint)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (azure-ip-masq-merger)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (azure-ip-masq-merger)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0PkojagAAAABYZku6Ok6KTZIEgY2vVJceTVNQMzExMDAwMTAyMDQ5AEVkZ2U=
Run govulncheck (azure-ip-masq-merger)
Failed to restore: Cache service responded with 400
Run govulncheck (azure-ip-masq-merger)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (azure-ip-masq-merger)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Run govulncheck (cilium-log-collector)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (cilium-log-collector)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0REojagAAAACcSEwEJ43rTaPkYdM0j4lUUEhMMzBFREdFMDEwOQBFZGdl
Run govulncheck (cilium-log-collector)
Failed to restore: Cache service responded with 400
Run govulncheck (cilium-log-collector)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (tools/azure-npm-to-cilium-validator)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (tools/azure-npm-to-cilium-validator)
Failed to restore: Cache service responded with 400
Run govulncheck (tools/azure-npm-to-cilium-validator)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (azure-ipam)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (azure-ipam)
Failed to restore: Cache service responded with 400
Run govulncheck (azure-ipam)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0XUojagAAAADx5pbwjdD3SKcebNomJFjzUEhMMzBFREdFMDIyMABFZGdl
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Failed to restore: Cache service responded with 400
Run govulncheck (bpf-prog/ipv6-hp-bpf)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (azure-iptables-monitor)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (azure-iptables-monitor)
Failed to restore: Cache service responded with 400
Run govulncheck (azure-iptables-monitor)
Both go-version and go-version-file inputs are specified, only go-version will be used
Run govulncheck (azure-iptables-monitor)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Run govulncheck (.)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run govulncheck (.)
Failed to restore: Cache service responded with 400
Run govulncheck (.)
Both go-version and go-version-file inputs are specified, only go-version will be used