chore(deps): bump k8s.io/client-go from 0.30.2 to 0.32.2

[dependabot]

Bumps k8s.io/client-go from 0.30.2 to 0.32.2.

Commits

• 86ff7a1 Update dependencies to v0.32.2 tag
• 4765ade Merge remote-tracking branch 'origin/master' into release-1.32
• 692a511 Drop use of winreadlinkvolume godebug option
• 9df5099 Merge remote-tracking branch 'origin/master' into release-1.32
• 120beb2 Revert to go1.22 windows filesystem stdlib behavior
• 55d23e2 Align fake client-go clients with the main interface
• 646e79b Run codegen
• c475fe0 Generify fake clientsets
• 955401c Merge pull request #128407 from ndixita/pod-level-resources
• eddb107 Merge pull request #127857 from Jefftree/cle-v1alpha2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Update the Kubernetes client-go and related dependencies to v0.32.2, and update the go toolchain to version 1.23.6.

Chores:

• Update the Kubernetes client-go and related dependencies to v0.32.2.
• Update the go toolchain to version 1.23.6.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the k8s.io/client-go dependency from version 0.30.2 to 0.32.2. This involves updating the go.mod and go.sum files to reflect the new version and its transitive dependencies.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update k8s.io/client-go and related dependencies in go.mod.	Update k8s.io/client-go to v0.32.2. Update k8s.io/apimachinery to v0.32.2. Update k8s.io/api to v0.32.2. Update k8s.io/cli-runtime to v0.30.2 (no change). Update k8s.io/kube-openapi. Update k8s.io/utils. Update sigs.k8s.io/json. Update golang.org/x/net. Update golang.org/x/oauth2. Update golang.org/x/sys. Update golang.org/x/term. Update golang.org/x/text. Update google.golang.org/protobuf. Update github.com/go-openapi/jsonpointer. Update github.com/go-openapi/swag. Update sigs.k8s.io/structured-merge-diff/v4.	go.mod
Update checksums for the updated and new dependencies in go.sum.	Update checksums for k8s.io/client-go. Update checksums for k8s.io/apimachinery. Update checksums for k8s.io/api. Update checksums for other updated and new transitive dependencies.	go.sum
Update the go toolchain version.	Update the go toolchain version from go1.22.3 to go1.23.6.	go.mod

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[codiumai-pr-agent-free]

CI Feedback 🧐

(Feedback updated until commit 664cee0)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: Verify code

Failed stage: Verify Go code [❌]

Failure summary: The action failed because golangci-lint could not find any Go files to analyze. The error message suggests there might be issues with the Go module configuration. Specifically: Error: "context loading failed: no go files to analyze" The linter suggests running go mod tidy to resolve the issue There was also a warning about missing go.sum file which indicates potential module dependency issues

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 58: Adding to the cache ... 59: Successfully cached go to /opt/hostedtoolcache/go/1.22.3/x64 60: Added go to the path 61: Successfully set up Go version 1.22.3 62: [command]/opt/hostedtoolcache/go/1.22.3/x64/bin/go env GOMODCACHE 63: [command]/opt/hostedtoolcache/go/1.22.3/x64/bin/go env GOCACHE 64: /home/runner/go/pkg/mod 65: /home/runner/.cache/go-build 66: ##[warning]Restore cache failed: Dependencies file is not found in /home/runner/work/k8s-node-collector/k8s-node-collector. Supported file pattern: go.sum ... 233: [command]/usr/bin/tar xz --overwrite --warning=no-unknown-keyword --overwrite -C /home/runner -f /home/runner/work/_temp/107c0ba8-3830-4cef-ba5c-6c5a5888fc52 234: Installed golangci-lint into /home/runner/golangci-lint-1.57.2-linux-amd64/golangci-lint in 497ms 235: Prepared env in 682ms 236: ##[endgroup] 237: ##[group]run golangci-lint 238: Running [/home/runner/golangci-lint-1.57.2-linux-amd64/golangci-lint run --verbose] in [/home/runner/work/k8s-node-collector/k8s-node-collector] ... 239: level=info msg="[config_reader] Config search paths: [./ /home/runner/work/k8s-node-collector/k8s-node-collector /home/runner/work/k8s-node-collector /home/runner/work /home/runner /home /]" 240: level=info msg="[config_reader] Used config file .golangci.yml" 241: level=info msg="[lintersdb] Active 9 linters: [errcheck errorlint gocritic gosec gosimple govet ineffassign staticcheck unused]" 242: level=info msg="[loader] Go packages loading at mode 575 (compiled_files|exports_file|imports|name|types_sizes|deps|files) took 2.18804673s" 243: level=error msg="Running error: context loading failed: no go files to analyze: running `go mod tidy` may solve the problem" 244: level=info msg="Memory: 23 samples, avg is 25.3MB, max is 25.3MB" 245: level=info msg="Execution took 2.194815318s" 246: ##[error]golangci-lint exit with code 5