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

[release-1.30] Bump konnectivity-client to v0.30.3 #125085

Closed
wants to merge 851 commits into from

Conversation

azimjohn
Copy link
Contributor

What type of PR is this?

/kind feature

What this PR does / why we need it:

apiserver: no real changes to konnectivity-client
konnectivity-server and konnectivity-agent:
use go 1.21 (kubernetes-sigs/apiserver-network-proxy#550)
container images: default to non-root user (kubernetes-sigs/apiserver-network-proxy#564)
see Full delta

Which issue(s) this PR fixes:
kubernetes-sigs/apiserver-network-proxy#615

Special notes for your reviewer: None

Does this PR introduce a user-facing change? None

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

k8s-ci-robot and others added 30 commits May 6, 2024 01:08
…d_golint_package_name

chore: fix invalid package name by golint
…ontroller

the resourceclaim controller forgot to wait for podSchedulingSynced and templatesSynced
Fix +optional in comment for persistentVolumeClaimRetentionPolicy
…-non-csi-plugins

scheduler deprecates non-csi volumelimit plugins
…-things-take-2

Remove gcp in-tree cloud provider and credential providers
…-svc

Use endpointSlices for describing service endpoints
…containers-lifecycle

node_e2e: refactor RunTogether function
Use the generic/typed workqueue throughout
Signed-off-by: Matthias Bertschy <matthias.bertschy@gmail.com>
…letion

Add completion for kubectl set image
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
….io-components

Include k8s.io components with contextual logging in logcheck.conf
Signed-off-by: Monis Khan <mok@microsoft.com>
scheduler: preallocation for NodeToStatusMap
(No changes from before they were deleted, and thus they don't
actually compile because of missing provider code.)
@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 23, 2024
@k8s-ci-robot
Copy link
Contributor

Hi @azimjohn. Thanks for your PR.

I'm waiting for a kubernetes 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 k8s-ci-robot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label May 23, 2024
@k8s-ci-robot k8s-ci-robot requested review from bart0sh, bowei and a team May 23, 2024 10:20
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: azimjohn
Once this PR has been reviewed and has the lgtm label, please assign cheftako, deads2k, pohly, sttts 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 area/apiserver area/cloudprovider area/dependency Issues or PRs related to dependency changes area/provider/gcp Issues or PRs related to gcp provider sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/node Categorizes an issue or PR as relevant to SIG Node. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 23, 2024
@azimjohn azimjohn changed the base branch from master to release-1.30 May 23, 2024 10:22
@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 23, 2024
@k8s-ci-robot
Copy link
Contributor

This cherry pick PR is for a release branch and has not yet been approved by Release Managers.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved (/lgtm + /approve) by the relevant OWNERS.

If you didn't cherry-pick this change to all supported release branches, please leave a comment describing why other cherry-picks are not needed to speed up the review process.

If you're not sure is it required to cherry-pick this change to all supported release branches, please consult the cherry-pick guidelines document.

AFTER it has been approved by code owners, please leave the following comment on a line by itself, with no leading whitespace: /cc kubernetes/release-managers

(This command will request a cherry pick review from Release Managers and should work for all GitHub users, whether they are members of the Kubernetes GitHub organization or not.)

For details on the patch release process and schedule, see the Patch Releases page.

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 the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 23, 2024
@k8s-ci-robot
Copy link
Contributor

PR needs rebase.

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 size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels May 23, 2024
@azimjohn
Copy link
Contributor Author

wrong branch, will re-open from release-1.30

@azimjohn azimjohn closed this May 23, 2024
@azimjohn azimjohn deleted the konnectivity-1.30 branch May 23, 2024 12:46
@cici37
Copy link
Contributor

cici37 commented May 28, 2024

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/apiserver area/cloudprovider area/dependency Issues or PRs related to dependency changes area/provider/gcp Issues or PRs related to gcp provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/feature Categorizes issue or PR as related to a new feature. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/node Categorizes an issue or PR as relevant to SIG Node. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet