Bump the k8s-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the k8s-dependencies group with 2 updates in the / directory: k8s.io/component-base and k8s.io/klog/v2.

Updates k8s.io/component-base from 0.30.1 to 0.30.2

Commits

• 244709c Update dependencies to v0.30.2 tag
• See full diff in compare view

Updates k8s.io/klog/v2 from 2.120.1 to 2.130.1

Release notes

Sourced from k8s.io/klog/v2's releases.

Prepare klog release for Kubernetes v1.31 (Take 2)

What's Changed

• data race: avoid unprotected access to sb.file by @​pohly in kubernetes/klog#408

Full Changelog: kubernetes/klog@v2.130.0...v2.130.1

Prepare klog release for Kubernetes v1.31 (Take 1)

What's Changed

• chore(*): fix spelling of Intel Corporation by @​jsoref in kubernetes/klog#399
• build: fix some linter warnings by @​pohly in kubernetes/klog#402
• examples: fix linter warning by @​pohly in kubernetes/klog#406
• Do not acquire lock for file.Sync() fsync call by @​1978629634 in kubernetes/klog#404
• ktesting: tone down warning about leaked test goroutine by @​pohly in kubernetes/klog#401

New Contributors

• @​jsoref made their first contribution in kubernetes/klog#399
• @​1978629634 made their first contribution in kubernetes/klog#404

Full Changelog: kubernetes/klog@v2.120.1...v2.130.0

Commits

• 75663bb Merge pull request #408 from pohly/klog-flush-sync-fix
• 2327d4c data race: avoid unprotected access to sb.file
• 16c7d26 Merge pull request #401 from pohly/ktesting-warning-delay
• cd24012 ktesting: tone down warning about leaked test goroutine
• 2ee202a Merge pull request #404 from 1978629634/fsync-freelock
• 79575d8 Do not acquire lock for file.Sync() fsync call
• 7af45d6 Merge pull request #406 from pohly/linter
• d008cfe examples: fix linter warning
• ab53041 Merge pull request #402 from pohly/linter-issues
• ff7c070 build: fix some linter warnings
• Additional commits viewable in compare view

Updates k8s.io/apimachinery from 0.30.1 to 0.30.2

Commits

• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[k8s-ci-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-csi 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.

[jsafrane]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], jsafrane

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jsafrane]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment