Update Go modules #678
Update Go modules #678
Conversation
![red-hat-konflux[bot]](https://avatars.githubusercontent.com/in/296509?s=60&v=4){kind=small}
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
red-hat-konflux
bot
added
the
dependencies
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
|
Hi @red-hat-konflux[bot]. Thanks for your PR. I'm waiting for a netobserv member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
This PR contains the following updates:
9aa4983->7625b7fv0.5.0->v0.6.0v1.0.1->v1.0.2v0.16.0->v0.18.0v1.1.2->v1.3.0v1.2.0->v1.7.1v0.6.0->v0.8.0v2.0.4->v2.0.7v3.12.1->v3.12.2v5.9.0->v5.9.11v1.8.0->v1.9.0v2.7.0->v2.8.0v0.5.1->v0.6.0v0.21.0->v0.21.1v0.23.0->v0.23.1v0.6.0->v0.7.0v1.5.0->v1.5.3v2.25.1->v2.26.3v1.17.11->v1.18.0v2.2.9->v2.2.10v0.3.0->v0.4.0v0.7.7->v0.9.05fc2798->1e4dbdfv7.0.87->v7.0.91f37122a->526b43e95b6ca5->14237a8v4.1.21->v4.1.22v0.2.2->v0.2.3v1.21.1->v1.22.0v0.6.1->v0.6.2v0.62.0->v0.63.0v0.15.1->v0.16.1v1.8.2-0.20201028100903-3245b3267b24->v1.99.0v0.3.1-0.20231027162144-83e5e0097c91->v0.5.10v1.8.1->v1.9.1v2.27.2->v2.27.6v0.4.1->v0.5.0v0.12.0->v0.14.05f08fbb->686a1a21.23.5->1.24.2v1.34.0->v1.35.0v1.32.0->v1.35.0v1.29.0->v1.35.0v1.34.0->v1.35.0v1.33.0->v1.35.0v1.34.0->v1.35.0v1.34.0->v1.35.0v1.34.0->v1.35.0v1.32.0->v1.35.0v1.34.0->v1.35.0v1.9.0->v1.11.0v0.35.0->v0.37.08a7402a->7e4ce0av0.36.0->v0.39.0v0.24.0->v0.29.0v0.30.0->v0.32.0v0.29.0->v0.31.0v0.22.0->v0.24.0v0.7.0->v0.11.01a7da9e->7b384671a7da9e->7b38467v1.70.0->v1.72.0v1.36.5->v1.36.6v0.32.3->v0.33.0v0.32.3->v0.33.0v0.32.3->v0.33.0v0.32.1->v0.33.0v1.2.0->v1.3.0v0.20.0->v0.20.49aa6b5e->cfa47c3v4.6.0->v4.7.0Release Notes
agoda-com/opentelemetry-logs-go (github.com/agoda-com/opentelemetry-logs-go)
v0.6.0Compare Source
Changed
v0.5.1Compare Source
cenkalti/hub (github.com/cenkalti/hub)
v1.0.2Compare Source
cilium/ebpf (github.com/cilium/ebpf)
v0.18.0Compare Source
Initial Windows Support
This release adds support for eBPF on Windows through the eBPF for Windows runtime. Users must run a recent build of the
mainbranch of eBPF for Windows, version 0.20.0 is not supported.See the documentation and how to contribute to the Windows port.
Supported:
Not supported:
The Windows port is still very new and won't be as performant or stable as the Linux part of the code base. There is also no guarantee of stability at the moment.
Build System Improvements
-verboseflag to bpf2go and gentypes toolsV=environment variableDocumentation
Bugfixes
Breaking Changes
ebpf:
SanitizeNamefunction. Map and program names are now automatically sanitized.What's Changed
binary.Readwithbinary.Decodeinsysenc.Unmarshalby @kolesnikovae in https://github.com/cilium/ebpf/pull/1713New Contributors
Full Changelog: cilium/ebpf@v0.17.3...v0.18.0
v0.17.3Compare Source
Fixes for a data race in
btf.Spec.Copy(thanks @paulcacheux) and a buffer overflow when running 32-bit user space on a 64-bit kernel (thanks @kolyshkin).What's Changed
unix.Auxvby @tklauser in https://github.com/cilium/ebpf/pull/1665parseLineInfoRecordsby @paulcacheux in https://github.com/cilium/ebpf/pull/1657(*mutableTypes).copyby @paulcacheux in https://github.com/cilium/ebpf/pull/1673Full Changelog: cilium/ebpf@v0.17.2...v0.17.3
v0.17.2Compare Source
Another minor release to ship some bug fixes, notably for attaching bpf programs to symbols in kernel modules, and for reusing data sections across multiple Collections.
All users are encouraged to upgrade!
Features
Bug Fixes
Other Changes
flattenInstructionsby @paulcacheux in https://github.com/cilium/ebpf/pull/1647Thanks to all who contributed and reported issues!
Full Changelog: cilium/ebpf@v0.17.1...v0.17.2
v0.17.1: Hotfix: don't retry endlessly on verifier errors on kernels <6.4Compare Source
During the prior removal of
ProgramOptions.LogSizein v0.16, the tests weren't updated to exercise the retry logic. With the last-minute addition ofProgramOptions.LogSizeStart, a bug was introduced that would cause program loads to retry indefinitely without ever growing the buffer in case of a verifier error on kernels before 6.4. This is now fixed, and the tests were updated to exercise the retry logic.v0.17.0: Global Variables, Decl Tags, and packagepinCompare Source
Note: the hotfix release 0.17.1 is out. Users are highly encouraged to upgrade.
As we close the door on the year 2024, we're also wrapping up the ebpf-go v0.17 development cycle. This release represents a large body of work and is our largest feature release since BTF.
Users are, as always, highly encouraged to upgrade, and we're looking forward to hearing your feedback on the new Global Variables API. We've been putting this interface trough its paces internally, along with a few eager community members, and we're ready to let the wider community make use of it.
This release also marks the end of our Go 1.21 support; Go 1.22 is required going forward.
Breaking Changes
Before we get to the fun stuff, we need to call out a few breaking changes:
Global variables with a
staticqualifier can no longer be rewritten usingCollectionSpec.RewriteConstants()! See the section on global variables under major features below.program: remove LogSize and VerifierError.Truncated by @lmb in https://github.com/cilium/ebpf/pull/1526
prog: add ProgramOptions.LogSizeStart to obtain full log after verifier bug by @ti-mo in https://github.com/cilium/ebpf/pull/1630
The
ProgramOptions.LogSizefield was deprecated and a no-op since 0.16 and has now been removed completely. In its place, a new field was added to obtain full verifier logs when the verifier hits an internal bug. TheProgramOptions.LogSizeStartfield controls the starting size of the log buffer. Use this if you have a good understanding of the log size you're expecting, or if you're trying to pull out the full log when the verifier hits an internal bug. The error string now also contains some hints about what happened and how to handle this situation.map: remove MapSpec.Freeze field by @ti-mo in https://github.com/cilium/ebpf/pull/1558
elf_reader: don't use BPF_F_RDONLY_PROG flag to trigger map freezing by @ti-mo in https://github.com/cilium/ebpf/pull/1568
The Freeze field was ambiguous from the start, and has been a source of subtle bugs over the years. Automatic map freezing is now done based solely on map name (.(ro)data prefix). If you were manually setting this flag, consider using a conventional map name instead.
info: expose ksym info and func info by ProgramInfo by @Asphaltt in https://github.com/cilium/ebpf/pull/1576
info: expose more prog jited info by @Asphaltt in https://github.com/cilium/ebpf/pull/1598
Some ext_info types in package btf were redefined to enable pulling raw func and line infos out of
Program.Info(). These were all types without methods and all unexported fields, but calling them out regardless in case someone's doingunintendedadvanced things with BTF.kallsyms: change Modules caching strategy, cache address lookups by @ti-mo in https://github.com/cilium/ebpf/pull/1590
Users attaching bpf programs to kernel symbols should see a marked decrease in allocations made in the library during program creation in the general case. Only used entries are now cached, making kallsyms lookups on subsequent program loads free. In the pathological case (new kernel symbols on every load), scanning is repeated, resulting in more CPU time being used instead of holding on to all kallsyms symbols indefinitely.
ProgramSpec.KernelModule()was unexported until further notice.Also, bpf2go users should now be able to generate Go bindings as unprivileged users once again. Oops!
Major Features
Easy global variables: introducing
ebpf.VariableSpecandebpf.VariableThis has been a frequent ask in the community for years, so we finally bit the bullet and committed to an API to interact with global bpf variables through
CollectionSpec.VariablesandCollectionSpec.Variables. We've published a small guide over on ebpf-go.dev/concepts/global-variables that details how to use them, so we're not going to reiterate here.See the documentation on the use of the
staticqualifier! These are no longer considered global variables, and can't be modified at runtime.bpf2go now also generates objects to be used with
CollectionSpec.Assignand.LoadAndAssign(), and also emits Go type declarations for C types used as bpf C variables. Our test coverage was somewhat lacking for the latter, please drop something on the issue tracker if you're noticing surprising bpf2go output.Note that it's currently not possible to manually create a
VariableSpecand wire it up to aCollectionSpec, so if you were previously relying on e.g. manually assembling aCollectionSpecand usingRewriteConstants()in tests, this will no longer work. This may land as the API crystallizes and we settle on a good mechanism to enable this. Please reach out on the Cilium Slack if you'd like to see this happen.Tags!
As you'll notice, the
btf.Struct,btf.Union,btf.Member,btf.Typedef,btf.Funcandbtf.Varhave gained a new field:Tags! Set one or more tags on these objects from bpf C using__attribute__((btf_decl_tag("mytag")))andyou'll find
Tagsbeing populated in Go.There's also the
btf.Func.ParamTagsfield that holds tags declared on individual function parameters. These are part of theFuncsince they appear only in the function prototype, not in the parameter type itself, since those can appear in many different types. (it does get confusing!)Also, an honorable mention to
btf.TypeTag, which has now been exported. This allows tagging pointers with an arbitrary string value and is mainly used by the Linux verifier to tag kernel pointers, see the__kptrand__kptr_refmacros in Linux'bpf_helpers.h.Pins!
We've added a new root-level package
pin, which currently features theLoad()andWalkDir()functions. Since allLoadPinned*functions in the library now check for the underlying object's type, we've repurposed the machinery to allow loading an opaque pin and returning a Go object of the right type.WalkDirdoes what it says on the tin, it walks bpffs directories and invokes a callback that received the loaded object. Super convenient!Minor Features
We've also added a handful of minor features during this release:
bpf_prog_infofields inProgramInfoby @tyrone-wu in https://github.com/cilium/ebpf/pull/1512Other Changes
Last but not least, there's bugfixes, CI changes and some internal refactoring that happened to eventually make ebpf-go work with ebpf-for-windows. See individual PRs for more context. Stay tuned!
objNameAllowsDot, return *btf.Var fromVariable{Spec}.Type()by @ti-mo in https://github.com/cilium/ebpf/pull/1612epoll.Waitby using sentinel errors by @def in https://github.com/cilium/ebpf/pull/1619New Contributors
Full Changelog: cilium/ebpf@v0.16.0...v0.17.0
containernetworking/cni (github.com/containernetworking/cni)
v1.3.0Compare Source
What's Changed
This adds a new config flag
loadPluginsFromFolder - if present, for a given named network bar, plugin configuration objects will be loaded from<path-to-bar-network-config-file>/bar/xxx.conf. This may be useful for vendors providing chained plugins: you can add your plugin to a chain without needing to edit the file in-place.New Contributors
Full Changelog: containernetworking/cni@v1.2.3...v1.3.0
v1.2.3: libcni v1.2.3Compare Source
This is a minor release to correct a divergence between the specification and libcni. In this case, the specification was updated, as it concerns a new feature, GC, that is not yet deployed.
What's Changed
v1.2.2: libcni v1.2.2Compare Source
What's Changed
Full Changelog: containernetworking/cni@v1.2.1...v1.2.2
v1.2.1: CNI Spec v1.1 / libcni v1.2.1Compare Source
This is a minor release that fixes some small bugs:
Improvements
Bug fixes:
DelNetwork, and allows CRIO tests to bumpv1.2.0: CNI spec v1.1 / libcni v1.2.0Compare Source
This is libcni v1.2.0, which releases the new CNI spec version v1.1.0.
Major changes:
GC verb
The GC verb allows runtimes to specify the set of known-good attachments, allowing plugins to clean up stale and leaked resources such as IPAM reservations. Libcni will also synthesize a CNI DEL for any stale cached attachments, so all users will have a form of GC, even if their plugins do not support CNI v1.1
STATUS verb
The STATUS verb allows a plugin to report its readiness to accept ADD requests. Runtimes such as containerd and cri-o will no longer have to rely merely on the presence of a CNI configuration file to determine network readiness.
Version negotiation
CNI configurations may now contain multiple versions, so that an administrator can opportunistically update the protocol version without breaking older runtimes:
{ "cniVersion": "1.0.0", "cniVersions": ["1.0.0", "1.1.0"] }New fields
A number of new fields have been added to the result type:
Other improvements
containernetworking/plugins (github.com/containernetworking/plugins)
v1.7.1: CNI plugins v1.7.1Compare Source
What's Changed
(Administrative note: the GitHub release v1.7.0 somehow got split in to two immutable releases. v1.7.1 is a re-release that corrects the issue. Apologies for the trouble).
New features / options
Other improvements
Bug fixes
New Contributors
Full Changelog: containernetworking/plugins@v1.6.2...v1.7.1
v1.7.0Compare Source
v1.6.2Compare Source
(administrative note: release v1.6.1 was somehow double-created in GitHub; v1.6.2 is identical but fixes the duplication.)
What's Changed
Full Changelog: containernetworking/plugins@v1.6.0...v1.6.2
v1.6.1Compare Source
v1.6.0: CNI plugins v1.6.0Compare Source
This is the v1.6.0 release of the CNI community plugins.
Changelog
Important
New features
Configuration
📅 Schedule: Branch creation - "after 5am on sunday" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
To execute skipped test pipelines write comment
/ok-to-test.This PR has been generated by MintMaker (powered by Renovate Bot).