Skip to content

chore(all): update kubernetes packages to v0.33.1 #5333

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Jun 2, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
k8s.io/apimachinery v0.32.4 -> v0.33.1 age adoption passing confidence
k8s.io/client-go v0.32.4 -> v0.33.1 age adoption passing confidence

Release Notes

kubernetes/apimachinery (k8s.io/apimachinery)

v0.33.1

Compare Source

v0.33.0

Compare Source

v0.32.5

Compare Source

kubernetes/client-go (k8s.io/client-go)

v0.33.1

Compare Source

v0.33.0

Compare Source

v0.32.5

Compare Source


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: connectgateway/go.sum
Command failed: install-tool golang 1.21.13

@renovate-bot renovate-bot requested review from a team as code owners June 2, 2025 02:54
@product-auto-label product-auto-label bot added the samples Issues that are directly related to samples. label Jun 2, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @renovate-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

As gemini-code-assist, I've reviewed this pull request. This PR, automatically generated by renovate-bot, focuses on updating the versions of the core Kubernetes Go client libraries used within the connectgateway module. It specifically targets k8s.io/apimachinery and k8s.io/client-go, upgrading them from version v0.32.4 to v0.33.1. This is a standard dependency update to ensure the project utilizes recent versions of these essential Kubernetes components, potentially incorporating bug fixes, performance improvements, or new features from the upstream libraries.

Highlights

  • Kubernetes Dependency Update: The primary change in this PR is the update of the k8s.io/apimachinery and k8s.io/client-go Go modules to version v0.33.1.
  • Automated Update: This pull request was automatically generated by renovate-bot to keep dependencies up to date.

Changelog

  • connectgateway/go.mod
    • Updated k8s.io/apimachinery dependency from v0.32.4 to v0.33.1 (line 11).
    • Updated k8s.io/client-go dependency from v0.32.4 to v0.33.1 (line 12).
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


Dependencies shift,
Versions climb, a steady rise,
Keep the code current.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This PR, generated by Mend Renovate, updates k8s.io/apimachinery and k8s.io/client-go from v0.32.4 to v0.33.1 in the connectgateway/go.mod file.

While keeping dependencies up-to-date is crucial, the upgrade to v0.33.x for these Kubernetes libraries is particularly noteworthy because the v0.33.0 release (which is part of this upgrade path) introduced breaking changes by removing several previously deprecated packages.

A non-exhaustive list of removed packages includes:

  • From k8s.io/client-go: tools/events, util/cert, util/clock, util/flowcontrol, util/integer, util/jsonpath, util/sets, util/testing, util/uuid, util/wait, util/workqueue.
  • From k8s.io/apimachinery: pkg/util/clock, pkg/util/diff, pkg/util/integer, pkg/util/rand, pkg/util/uuid.

Most of these removed packages have replacements, often found in k8s.io/utils or other locations within apimachinery or client-go (e.g., k8s.io/client-go/tools/record for tools/events, k8s.io/apimachinery/pkg/util/sets for client-go/util/sets).

The connectgateway/get_namespace.go sample (provided in the PR context) does not appear to directly import these specific removed packages. However, the GoogleCloudPlatform/golang-samples repository is extensive. It's vital to ensure that no Go samples relying on these Kubernetes libraries are adversely affected by these removals.

My primary recommendation is to conduct thorough testing across all relevant samples before merging this update.

Summary of Findings

  • Potential Breaking Changes in Kubernetes Library Update: The update to k8s.io/apimachinery and k8s.io/client-go to v0.33.1 incorporates the v0.33.0 release. This version removed several deprecated packages (e.g., from k8s.io/client-go/util/... and k8s.io/apimachinery/pkg/util/...). This poses a risk of breaking changes if any code in the golang-samples repository still uses these removed packages. Thorough testing across all affected Go samples is required to ensure compatibility and prevent regressions.

Merge Readiness

This pull request updates core Kubernetes client libraries to newer versions. Due to the significant changes in v0.33.0 (specifically, the removal of several deprecated packages), there is a potential for breaking changes if any Go samples in this repository were using those removed packages.

I recommend that this PR not be merged until the following are confirmed:

  1. Comprehensive CI tests pass for all relevant Go samples that might be affected by this update.
  2. Manual testing or validation (if applicable for samples) confirms no regressions in functionality, especially for the connectgateway sample and any others that heavily rely on client-go or apimachinery.
  3. The author or maintainers have assessed the impact of these removed packages across the repository and confirmed that all necessary code adaptations (if any) have been made or are not needed.

As a reviewer, I am not authorized to approve pull requests. Please ensure further review and approval from maintainers after these checks are satisfactorily completed.

Comment on lines +11 to +12
k8s.io/apimachinery v0.33.1
k8s.io/client-go v0.33.1

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This update to v0.33.1 for k8s.io/apimachinery and k8s.io/client-go is a notable version bump. The v0.33.0 release, which is part of this upgrade path, removed a number of previously deprecated packages (e.g., various subpackages under k8s.io/client-go/util/... and k8s.io/apimachinery/pkg/util/... which have replacements in other locations like k8s.io/utils or elsewhere within the main libraries).

Could you please ensure that the connectgateway sample, and any other Go code in this repository relying on these Kubernetes libraries, are thoroughly tested with these new versions? This includes:

  • Verifying successful compilation across all relevant Go modules (checking for broken imports due to removed packages).
  • Confirming that all relevant functionalities remain operational through existing tests or manual validation where necessary.

Comprehensive testing is essential due to the potential for breaking changes introduced by the removed packages in v0.33.0.

Copy link

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@telpirion telpirion self-assigned this Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
samples Issues that are directly related to samples.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants