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.

Sign up for GitHub

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

Jump to bottom

[release-1.30] [go] Bump images, dependencies and versions to go 1.22.2 and distroless iptables #124829

Merged
merged 1 commit into from
May 15, 2024
Merged

[release-1.30] [go] Bump images, dependencies and versions to go 1.22.2 and distroless iptables #124829

merged 1 commit into from
May 15, 2024

Conversation

cpanato
Copy link
Member

@cpanato cpanato commented May 12, 2024

What type of PR is this?

/kind feature

What this PR does / why we need it:

  • Bump images, dependencies and versions to go 1.22.3 and distroless iptables

Which issue(s) this PR fixes:

Part of kubernetes/release#3597

/assign @MadhavJivrajani @liggitt @puerco @saschagrunert
cc @kubernetes/release-managers

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Kubernetes is now built with go 1.22.3

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

@k8s-ci-robot k8s-ci-robot added the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label May 12, 2024
@k8s-ci-robot k8s-ci-robot added this to the v1.30 milestone May 12, 2024
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 12, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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 k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels May 12, 2024
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject area/test sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 12, 2024
@cpanato cpanato mentioned this pull request May 12, 2024
Closed
24 tasks
@saschagrunert
Copy link
Member

/retest

@saschagrunert
Copy link
Member

The legacy cloud providers have been removed in #124767.

@cpanato
Copy link
Member Author

cpanato commented May 13, 2024

The legacy cloud providers have been removed in #124767.

we should cherry pick to the release branches, lets confirm that and i will cherry pick

@liggitt
Copy link
Member

liggitt commented May 13, 2024

The legacy cloud providers have been removed in #124767.

we should cherry pick to the release branches, lets confirm that and i will cherry pick

the error is weird, it's complaining about master branch which shouldn't be relevant here... right?

liggitt referenced this pull request May 13, 2024
@carlory
remove legacycloudproviders from staging
07c8d35
@liggitt
Copy link
Member

liggitt commented May 13, 2024

/lgtm
/approve
(for all the actual changes in this PR)

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 13, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 24ec4171f84f882e0b2b15388a89f97ef162e689

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 13, 2024
@carlory carlory mentioned this pull request May 14, 2024
Closed
@carlory carlory mentioned this pull request May 14, 2024
Merged
@saschagrunert
Copy link
Member

/retest

@cpanato
Copy link
Member Author

cpanato commented May 14, 2024

@saschagrunert @liggitt all good, i think we need to wait until the patch releases are out

@k8s-ci-robot k8s-ci-robot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. and removed do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. labels May 15, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, liggitt, saschagrunert

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:

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 merged commit 5c67fe5 into kubernetes:release-1.30 May 15, 2024
19 checks passed
@cpanato cpanato deleted the update-go-rel-130 branch May 15, 2024 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@saschagrunert saschagrunert saschagrunert approved these changes

@dims dims Awaiting requested review from dims

@jeremyrickard jeremyrickard Awaiting requested review from jeremyrickard

Assignees

@liggitt liggitt

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject area/test cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
v1.30
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@cpanato @k8s-ci-robot @saschagrunert @liggitt