-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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 master into dev-1.20 to keep in sync #24290
Merge master into dev-1.20 to keep in sync #24290
Conversation
[zh] add missing links in/zh/docs/home/contribute
/language id
…eachable-toleration-seconds k8s-apiserver input parameters in the subsection describing the DefaultTolerationSeconds admission controller
fix toggle button
We currently have quite some contents duplicated between the concepts and the reference section, which is not good. This PR is an effort to remove the duplicated content from the two pages while providing links for readers to check the reference easily.
Update configure-upgrade-etcd.md
[en] fix code block rendering mistake
Co-authored-by: bells17 <bells171@gmail.com>
…known_labels Link to well-known labels rather than repeating the list
translate /zh/docs/tasks/configmap-secret/managing-secret-using-kubectl.md
The English content was COMPLETELY REWRITTEN for DAMN REASONS.
This may be intuitive for most, but the existing phrasing read to me as if `bind` were a special-case verb that _required_ me to explicitly state which Roles or ClusterRoles it should apply to. > You can only create/update a role binding if you […] or if you have > been authorized to perform the bind verb on the referenced role. > Grant them permissions needed to bind a particular role […] > explicitly, by giving them permission to perform the bind verb on the > particular Role (or ClusterRole).
Contex to Context
Fix 404 issues
namespaces FR : fixing typos and improving a few points
Fixed typo s/kustomizae/kustomize
Fixed typo s/kustomizae/kustomize
Hey @jimangel @savitharaghunathan, wondering if we can get your feedback on how to resolve |
I believe we ran into this last cycle and chose to ignore it. k8s-ci-robot doesn't like However, much like this PR, a merge PR will inevitably contain a unique PR number in the commit message. This is what we are seeing from localization merge PRs. I will double check tomorrow, but we most likely can ignore. |
Thanks @jimangel ! I do remember now that we ran into something similar in the last release. Is there an issue already created for this from last time? If not, I can follow up and create one. Or if the behavior is there on purpose, maybe we can enforce not adding @ or # in the comments and in the title of the PR somehow? Taking this PR(#23988) as an example. It looks like the invalid commit message was fixed, so the commit itself doesn't have |
Here's the link to PR kubernetes/test-infra#17893, that was created as a follow up in the test-infra repo. |
Thank you @savitharaghunathan! |
Following precedent from #21604 I manually removed the invalid commit label. I would like to get another /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jimangel 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: 16f3cbd3ca0e7811bf6cb9c78d2288f90f827a35
|
Merge master into dev-1.20 to keep in sync - SIG-Release 1.20 Docs team 09/30/20