Bump the k8s-dependencies group with 8 updates

[dependabot]

Bumps the k8s-dependencies group with 8 updates:

Package	From	To
k8s.io/api	0.36.1	0.36.2
k8s.io/apimachinery	0.36.1	0.36.2
k8s.io/apiserver	0.36.1	0.36.2
k8s.io/client-go	0.36.1	0.36.2
k8s.io/component-base	0.36.1	0.36.2
k8s.io/csi-translation-lib	0.36.1	0.36.2
k8s.io/streaming	0.36.1	0.36.2
sigs.k8s.io/apiserver-network-proxy/konnectivity-client	0.35.0	0.36.0

Updates k8s.io/api from 0.36.1 to 0.36.2

Commits

• 2f4cefd Update dependencies to v0.36.2 tag
• See full diff in compare view

Updates k8s.io/apimachinery from 0.36.1 to 0.36.2

Commits

• ae3f98e Update dependencies to v0.36.2 tag
• 2ec982d Merge pull request #139508lalitc375/automated-cherry-pick-of-#139480
• 6a88102 Fix wrong marking of errors
• See full diff in compare view

Updates k8s.io/apiserver from 0.36.1 to 0.36.2

Commits

• 6d47504 Update dependencies to v0.36.2 tag
• See full diff in compare view

Updates k8s.io/client-go from 0.36.1 to 0.36.2

Commits

• 877f535 Update dependencies to v0.36.2 tag
• See full diff in compare view

Updates k8s.io/component-base from 0.36.1 to 0.36.2

Commits

• 3393ee8 Update dependencies to v0.36.2 tag
• See full diff in compare view

Updates k8s.io/csi-translation-lib from 0.36.1 to 0.36.2

Commits

• 4d09395 Update dependencies to v0.36.2 tag
• See full diff in compare view

Updates k8s.io/streaming from 0.36.1 to 0.36.2

Commits

• See full diff in compare view

Updates sigs.k8s.io/apiserver-network-proxy/konnectivity-client from 0.35.0 to 0.36.0

Changelog

Sourced from sigs.k8s.io/apiserver-network-proxy/konnectivity-client's changelog.

Releasing a new version of apiserver-network-proxy

Please note this guide is only intended for the admins of this repository, and requires write access.

Creating a new release of network proxy involves releasing a new version of the client library (konnectivity-client) and new images for the proxy agent and server. Generally we also want to upgrade kubernetes/kubernetes with the latest version of the images and library, but this is a GCE specific change.

1. If increasing the minor version (the y in x.y.z), a new release branch must be created. The name of this branch should be release-x.y where x and y correspond to the major and minor release numbers for apiserver-network-proxy. For example, if increasing the apiserver-network-proxy from verision 0.35.1 to 0.36.0 a new branch should be created named release-0.36.

   After making the new tag for the release version, use the following command to create the new branch:

   # assuming a release version of 0.36.0
   export RELEASE=release-0.36
   git checkout -b "${RELEASE}"
   git push upstream "${RELEASE}"
   

2. The first step involves creating a new git tag for the release, following semver for go libraries. A tag is required for both the repository and the konnectivity-client library. For example releasing the 0.36.0 version will have two tags v0.36.0 and konnectivity-client/v0.36.0 on the appropriate commit. The minor version number (the y in x.y.z) should match the minor version of the Kubernetes version that is utilized by the apiserver-network-proxy. The patch level version number (the z in x.y.z) should increase by one unless a new minor version is being created, in which case it should be 0.

   In the master branch, choose the appropriate commit, and determine a patch version based on the required Kubernetes version and the current patch level.

   Example commands for HEAD of master branch. (Assumes you have git remote add upstream git@github.com:kubernetes-sigs/apiserver-network-proxy.git.)

   # Assuming v0.35.0 exists
   export TAG=v0.36.0
   export MESSAGE="Meaningful description of change."
   git fetch upstream
   
   git tag -a "${TAG}" -m "${MESSAGE}" upstream/master
   
   git tag -a "konnectivity-client/${TAG}" -m "${MESSAGE}" upstream/master
   
   git push upstream "${TAG}"
   
   git push upstream "konnectivity-client/${TAG}"
   
   

   In a release branch, the process is similar but corresponds to earlier minor versions.

   Example commands for HEAD of release-0.36 branch:

   # Assuming v0.35.0 exists, then it is on the release-0.36 branch
   export RELEASE=release-0.36
   export TAG=v0.36.0
   export MESSAGE="Meaningful description of change."
   git fetch upstream
   
   git tag -a "${TAG}" -m "${MESSAGE}" upstream/${RELEASE}
   
   git tag -a "konnectivity-client/${TAG}" -m "${MESSAGE}" upstream/${RELEASE}
   
   git push upstream "${TAG}"
   
   git push upstream "konnectivity-client/${TAG}"
   
   

... (truncated)

Commits

• e843261 Merge pull request #857 from kubernetes-sigs/dependabot/go_modules/gomod-depe...
• 64561d4 Merge pull request #856 from inerplat/fix/backend-dial-timeout-pending-dial
• 39caa18 chore(deps): bump github.com/prometheus/common
• 72fc545 Add optional backend dial timeout
• 9ee6775 Merge pull request #854 from kubernetes-sigs/dependabot/github_actions/golang...
• 734150d chore(deps): bump golangci/golangci-lint-action from 9.2.0 to 9.2.1
• 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 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign saad-ali for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[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.

Details

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.

[k8s-ci-robot]

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-csi-external-resizer-1-34-on-kubernetes-1-34	c4a805d	link	false	/test pull-kubernetes-csi-external-resizer-1-34-on-kubernetes-1-34

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.