chore(deps): update dependency cilium/hubble to v1.17.0

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
cilium/hubble	minor	1.16.6 -> 1.17.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

cilium/hubble (cilium/hubble)

v1.17.0

Compare Source

Minor Changes:

• Add support for automatic port-forwarding in Hubble CLI Replace kubectl-based port-forwarding with native implementation in Cilium CLI (cilium/cilium#35483, @​devodev)
• hubble: from and to cluster filters (cilium/cilium#33325, @​kaworu)
• hubble: Stop building 32-bit binaries (cilium/cilium#35974, @​michi-covalent)

Bugfixes:

• hubble: add printer for lost events (cilium/cilium#35208, @​aanm)
• hubble: consistently use v as prefix for the Hubble version (cilium/cilium#35891, @​rolinh)

CI Changes:

• Add Hubble CLI integration tests and skip running e2e/conformance on Hubble CLI only changes (cilium/cilium#33850, @​chancez)

Misc Changes:

• .github: add cache to cilium-cli and hubble-cli build workflows (cilium/cilium#34847, @​aanm)
• hubble: Add 'release' Make target (cilium/cilium#35561, @​michi-covalent)
• hubble: Combine hubble and hubble-bin make targets (cilium/cilium#35256, @​michi-covalent)
• hubble: remove outdated //go:build go1.18 tag (cilium/cilium#35174, @​tklauser)
• hubble: Use hubble-bin target to generate release binaries (cilium/cilium#35127, @​michi-covalent)
• make: add hubble cli to kind-image-fast-agent (cilium/cilium#35344, @​kaworu)
• Refactor Hubble as a cell (cilium/cilium#35206, @​kaworu)
• Remove deprecated call to DialContext in Hubble (cilium/cilium#34241, @​davchos)
• Use Go standard library slices package more extensively (cilium/cilium#34796, @​tklauser)
• chore(deps): update actions/setup-go action to v5.3.0 (#​1645, @​renovate[bot])
• chore(deps): update dependency cilium/cilium to v1.16.6 (#​1644, @​renovate[bot])
• chore(deps): update dependency cilium/cilium to v1.17.0 (#​1646, @​renovate[bot])
• Update stable release to 1.16.6 (#​1643, @​chancez)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[nicholasdille-bot]

Auto-approved because label type/renovate is present.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/hubble:1.17.0

📦 Image Reference ghcr.io/uniget-org/tools/hubble:1.17.0

digest	sha256:230c40b6cebd3cc23947fdbc45825a8303057d4cf5552c94dfefef1b82084eee
vulnerabilities
platform	linux/amd64
size	26 MB
packages	139

stdlib 1.23.4 (golang) pkg:golang/[email protected] Affected range >=1.23.0-0 <1.23.5 Fixed version 1.23.5 Description A certificate with a URI which has a IPv6 address with a zone ID may incorrectly satisfy a URI name constraint that applies to the certificate chain. Certificates containing URIs are not permitted in the web PKI, so this only affects users of private PKIs which make use of URIs. Affected range >=1.23.0-0 <1.23.5 Fixed version 1.23.5 Description The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2. Affected range >=1.23.0-0 <1.23.6 Fixed version 1.23.6 Description Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recovery of the private key when P-256 is used in any well known protocols.

[github-actions]

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/13204087238.

[github-actions]

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/13204087238.