-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Merge main into dev-1.25 branch: July 21st #35229
Merge main into dev-1.25 branch: July 21st #35229
Conversation
Co-authored-by: Tim Bannister <[email protected]>
This PR proposes an update to the PR review guidelines. The proposed change is about the use of the "Request changes" or the "Approve" option when finishing a PR review. Neither of these two options should be encouraged. We may want to encourage reviewers to always use "Comment", because: - "Request changes" status is sticky and unnecessary. Placing a "/hold" should be okay because we do respect opinions from all reviewers/approvers. The "Request changes" status can only be discarded by people with privileges. We see quite a few cases where the reviewer left a "Request changes" mark and forgot to revisit a PR. Such a sticky status is not friendly to contributors or peer reviewers. - The "Approve" option is confusing. It is not considered by the prow as an approval IIUC. The PR has to be approved again even if it has been "approved" this way.
I added access to the statement explaining cluster role permissions in this document to make it clearer.
This PR fix the wrong guide according to the commit bellow: [apiserver: support egress selection name 'controlplane' and deprecate 'master'](kubernetes/kubernetes@a0aebf9)
…urces/validating-webhook-configuration-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/extend-resources/validating-webhook-configuration-v1.md
There are deprecated kubelet flags related to garbage collection. These flags were listed in the `kubelet-garbage-collection.md` page, which was removed by b1573ad. Linking to the `kubelet` reference is not a good solution because users may still get confused what are the specific flags related to this behavior. This PR restores the table with the flags updated according to 1.24 version of `kubelet --help`.
All resource requests parse units the same way. Ephemeral storage previously had an upper case `K` as a valid unit but the kubernetes server can not parse this value. Similar to memory, add a statement regarding that a lowercase `m` will be accepted by the kubernetes server, but is probably an incorrect request.
…urces/pod-disruption-budget-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/policy-resources/pod-disruption-budget-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/policy-resources/pod-disruption-budget-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/policy-resources/pod-disruption-budget-v1.md [zh-cn]Update content/zh-cn/docs/reference/kubernetes-api/policy-resources/pod-disruption-budget-v1.md
[zh-cn] Translate PDB-v1
…with-affinity-anti-affinity.yaml [zh-cn]Update pod-with-affinity-anti-affinity.yaml
fix typo in job example
[zh-cn]Fixed a word in explore-intro.html
Signed-off-by: utkarsh-singh1 <[email protected]>
…webhook-configuration-v1 [zh-cn] Translate ValidatingWebhookConfiguration-v1
[zh-cn] resync /partners/_index.html
…-signed-images Updated the expired link for Configuration option
…te_KubeletCredentialProvider Fix KubeletCredentialProvider feature state
Fix wrong guide for egress selection.
/retitle Merge main into dev-1.25 branch: July 21st And I think the PR description is not clear. Seems like merge
Maybe this would be better
|
Sounds good. I just copied over the description from a previous branch sync PR |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: reylejano 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 |
HI just curious if we plan to merge main to dev-1.25, why don't we do dev-1.25...main ? Just to avoid confusion on if any personal commit added :) |
/lgtm
|
LGTM label has been added. Git tree hash: 78585554665b8c47d47e36e82fa797799745d678
|
This PR syncs the main branch with the dev-1.25 branch.