Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump the k8s-dependencies group across 1 directory with 6 updates #169

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 22, 2024

Bumps the k8s-dependencies group with 5 updates in the / directory:

Package From To
k8s.io/apimachinery 0.28.0 0.30.3
k8s.io/client-go 0.28.0 0.30.3
k8s.io/component-base 0.28.0 0.30.3
k8s.io/component-helpers 0.28.0 0.30.3
sigs.k8s.io/gateway-api 0.7.1 1.1.0

Updates k8s.io/apimachinery from 0.28.0 to 0.30.3

Commits
  • 37988e5 Merge remote-tracking branch 'origin/master' into release-1.30
  • c857a38 Update x/net for CVE-2023-45288
  • 0407311 followup to allow special characters
  • 25164f7 Merge pull request #123435 from tallclair/apparmor-ga
  • cbfe0a1 Merge pull request #123758 from liggitt/protobump
  • 21d26b6 Bump github.com/golang/protobuf v1.5.4, google.golang.org/protobuf v1.33.0
  • 0c29f84 Merge pull request #123385 from HirazawaUi/allow-special-characters
  • 60d24f2 Merge pull request #123708 from p0lyn0mial/upstream-const-watchlist-bookmark-...
  • 513d23a apimachinery/meta/types.go: define InitialEventsAnnotationKey const
  • 67cb3a8 Merge pull request #123413 from seans3/tunneling-spdy-websockets
  • Additional commits viewable in compare view

Updates k8s.io/client-go from 0.28.0 to 0.30.3

Commits
  • ece8c00 Update dependencies to v0.30.3 tag
  • 4e1652b Merge pull request #124694 from pmalek/backport-124553-to-release-1.30
  • 2daa31e fix(api): make LocalObjectReference.Name and HostAlias.IP required (#124553)
  • 2df4de1 Merge remote-tracking branch 'origin/master' into release-1.30
  • ade2ae2 Update x/net for CVE-2023-45288
  • b4632b7 Merge pull request #123932 from pohly/dra-api-resource-model-rename
  • 4467b1e Merge pull request #123909 from AkihiroSuda/fix-123906
  • 650f392 dra api: NodeResourceModel -> ResourceModel
  • 00e4609 api: NodeStatus: rename RuntimeClasses to RuntimeHandlers
  • 7ebe0ea Merge pull request #123180 from AkihiroSuda/rro
  • Additional commits viewable in compare view

Updates k8s.io/component-base from 0.28.0 to 0.30.3

Commits
  • de3cf26 Update dependencies to v0.30.3 tag
  • 0ac84ef Merge remote-tracking branch 'origin/master' into release-1.30
  • 2e27a0c Update x/net for CVE-2023-45288
  • ecbd1b6 Merge pull request #123732 from serathius/parallel-featureflags
  • b0a6e40 Merge pull request #123758 from liggitt/protobump
  • 0e945e3 Bump github.com/golang/protobuf v1.5.4, google.golang.org/protobuf v1.33.0
  • a626a5c Fix SetFeatureGateDuringTest handling of Parallel tests
  • 15d726c Merge pull request #123529 from thockin/go-workspaces
  • f3d8039 Fix up go.mod files after reviews
  • e3050ed Remove old gengo detritus
  • Additional commits viewable in compare view

Updates k8s.io/component-helpers from 0.28.0 to 0.30.3

Commits
  • f1326a1 Update dependencies to v0.30.3 tag
  • 7c78723 Merge remote-tracking branch 'origin/master' into release-1.30
  • 9e849fb Update x/net for CVE-2023-45288
  • baf8a99 Bump github.com/golang/protobuf v1.5.4, google.golang.org/protobuf v1.33.0
  • e6e24ac Merge pull request #123529 from thockin/go-workspaces
  • b61335b Fix up go.mod files after reviews
  • 4a7958d Remove old gengo detritus
  • 565efbc Re-vendor latest kube-openapi and gengo/v2
  • 1e267aa Generate go.work files
  • 866cab6 Merge pull request #123348 from hoskeri/update-go-x-crypto-19
  • Additional commits viewable in compare view

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

Release notes

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

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

What's Changed

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

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

What's Changed

New Contributors

Full Changelog: kubernetes/klog@v2.110.1...v2.120.0

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

What's Changed

New Contributors

Full Changelog: kubernetes/klog@v2.100.1...v2.110.1

Commits
  • 007e661 textlogger: allow caller to override stack unwinding
  • 2d08296 Merge pull request #396 from pohly/slog-helper
  • e4deee8 slog: use main logr package instead of logr/slogr
  • 5d1d2d5 add SetSlogLogger
  • 39afdba dependencies: logr v1.4.1
  • 2086216 Merge pull request #393 from kaisoz/add-safeptr
  • 881fa0b Add SafePtr wrapper
  • 8dd3f2e Merge pull request #395 from pohly/readme-update
  • d3dd725 docs: clarify relationship between different features
  • 761b630 Merge pull request #394 from pohly/owners-update
  • Additional commits viewable in compare view

Updates sigs.k8s.io/gateway-api from 0.7.1 to 1.1.0

Release notes

Sourced from sigs.k8s.io/gateway-api's releases.

v1.1.0

On behalf of Kubernetes SIG Network, we are pleased to announce the v1.1 release! This release includes the graduation of several features to GA, including both GRPCRoute and Service Mesh. We are also introducing several new experimental features, including Session Persistence and Gateway Client Cert Verification.

The following represents the changes since v1.0.0:

Standard Channel

GRPCRoute has Graduated to GA 🎉

GRPCRoute has graduated to GA (v1) and is now part of the Standard Channel. If you are already using the experimental version GRPCRoute, we recommend holding off on upgrading to the standard channel version of GRPCRoute until the controllers you're using have been updated to support GRPCRoute v1. Until then, it is safe to upgrade to the experimental channel version of GRPCRoute in v1.1 that includes both v1alpha2 and v1 API versions.

Leading Contributor: @​gnossen

Service Mesh Support has Graduated to GA 🎉

The standard for using Gateway API for Mesh has formally graduated to GA (v1) and is now part of the Standard Channel.

Service mesh support in Gateway API allows service mesh users to use the same API to manage ingress traffic and mesh traffic, reusing the same policy and routing interfaces. In Gateway API v1.1, routes (such as HTTPRoute) can now have a Service as a parentRef, to control how traffic to specific services behave. For more information, read the service mesh documentation or see the list of implementations.

Leading Contributors: @​howardjohn, @​keithmattix, @​kflynn, @​mikemorris

Conformance Profiles and Reports

The Conformance Reports API and the corresponding test suite have been graduated to GA. The Conformance report API has been expanded with the mode field (intended to specify the working mode of the implementation), and the gatewayAPIChannel (standard or experimental). The gatewayAPIVersion and gatewayAPIChannel are now filled in automatically by the suite machinery, along with a brief description of the testing outcome. The Reports have been reorganized in a more structured way, and the implementations can now add information on how the tests have been run and provide reproduction steps.

Leading Contributors: @​mlavacca, @​shaneutt

ParentRef Port field Graduated to GA

... (truncated)

Changelog

Sourced from sigs.k8s.io/gateway-api's changelog.

Release Process

Overview

The Gateway API project is an API project that has the following two components:

  • Kubernetes Custom Resource Definitions (CRDs)
  • Corresponding Go API in the form of sigs.k8s.io/gateway-api Go package

This repository is the home for both of the above components.

Versioning strategy

The versioning strategy for this project is covered in detail in the release documentation.

Releasing a new version

Writing a Changelog

To simplify release notes generation, we recommend using the Kubernetes release notes generator:

go install k8s.io/release/cmd/release-notes@latest
export GITHUB_TOKEN=your_token_here
release-notes --start-sha EXAMPLE_COMMIT --end-sha EXAMPLE_COMMIT --branch main --repo gateway-api --org kubernetes-sigs

This output will likely need to be reorganized and cleaned up a bit, but it provides a good starting point. Once you're satisfied with the changelog, create a PR. This must go through the regular PR review process and get merged into the main branch. Approval of the PR indicates community consensus for a new release.

Release Steps

The following steps must be done by one of the [Gateway API maintainers][gateway-api-team]:

For a PATCH release:

  • Create a new branch in your fork named something like <githubuser>/release-x.x.x. Use the new branch in the upcoming steps.
  • Use git to cherry-pick all relevant PRs into your branch.
  • Update pkg/generator/main.go with the new semver tag and any updates to the API review URL.
  • Run the following command BASE_REF=vmajor.minor.patch make generate which will update generated docs with the correct version info. (Note that you can't test with these YAMLs yet as they contain references to elements which wont exist until the tag is cut and image is promoted to production registry.)
  • Create a pull request of the <githubuser>/release-x.x.x branch into the release-x.x branch upstream (which should already exist since this is a patch release). Add a hold on this PR waiting for at least

... (truncated)

Commits
  • 690f754 Adding changelog for v1.1.0 (#3062)
  • a29ddd4 Contour conformance report updates (#3061)
  • 70ef27e Splitting Changelogs for each minor version (#3060)
  • 72e0a22 build(deps): bump sigs.k8s.io/controller-runtime in /gwctl (#3052)
  • 95d865e SessionPersistence field should have omitempty tag (#3059)
  • 6fc4f83 Adding changelog for v1.1.0-rc2 (#3046)
  • c8218ff Conformance test for listener isolation (#3047)
  • 654dde5 Make gwctl ReferenceGrant aware. Capture any errors observed while constructi...
  • cd175ec Conformance display profiles on gatewayapi docs (#2874)
  • ab850c3 Properly handle different versioned resources in gwctl (eg. v1beta1 v/s v1 AP...
  • 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 <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

Bumps the k8s-dependencies group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [k8s.io/apimachinery](https://github.com/kubernetes/apimachinery) | `0.28.0` | `0.30.3` |
| [k8s.io/client-go](https://github.com/kubernetes/client-go) | `0.28.0` | `0.30.3` |
| [k8s.io/component-base](https://github.com/kubernetes/component-base) | `0.28.0` | `0.30.3` |
| [k8s.io/component-helpers](https://github.com/kubernetes/component-helpers) | `0.28.0` | `0.30.3` |
| [sigs.k8s.io/gateway-api](https://github.com/kubernetes-sigs/gateway-api) | `0.7.1` | `1.1.0` |



Updates `k8s.io/apimachinery` from 0.28.0 to 0.30.3
- [Commits](kubernetes/apimachinery@v0.28.0...v0.30.3)

Updates `k8s.io/client-go` from 0.28.0 to 0.30.3
- [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md)
- [Commits](kubernetes/client-go@v0.28.0...v0.30.3)

Updates `k8s.io/component-base` from 0.28.0 to 0.30.3
- [Commits](kubernetes/component-base@v0.28.0...v0.30.3)

Updates `k8s.io/component-helpers` from 0.28.0 to 0.30.3
- [Commits](kubernetes/component-helpers@v0.28.0...v0.30.3)

Updates `k8s.io/klog/v2` from 2.100.1 to 2.120.1
- [Release notes](https://github.com/kubernetes/klog/releases)
- [Changelog](https://github.com/kubernetes/klog/blob/main/RELEASE.md)
- [Commits](kubernetes/klog@v2.100.1...v2.120.1)

Updates `sigs.k8s.io/gateway-api` from 0.7.1 to 1.1.0
- [Release notes](https://github.com/kubernetes-sigs/gateway-api/releases)
- [Changelog](https://github.com/kubernetes-sigs/gateway-api/blob/main/RELEASE.md)
- [Commits](kubernetes-sigs/gateway-api@v0.7.1...v1.1.0)

---
updated-dependencies:
- dependency-name: k8s.io/apimachinery
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/client-go
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/component-base
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/component-helpers
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: k8s-dependencies
- dependency-name: k8s.io/klog/v2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: k8s-dependencies
- dependency-name: sigs.k8s.io/gateway-api
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: k8s-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added area/dependency Issues or PRs related to dependency changes ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. labels Jul 22, 2024
@k8s-ci-robot k8s-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 22, 2024
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 22, 2024
@k8s-ci-robot
Copy link
Contributor

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.

@k8s-ci-robot
Copy link
Contributor

[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 xing-yang for approval. For more information see the Kubernetes Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jul 22, 2024
@k8s-ci-robot
Copy link
Contributor

@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-lib-volume-populator 696a577 link true /test pull-kubernetes-csi-lib-volume-populator

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.

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.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 10, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependency Issues or PRs related to dependency changes cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants