-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Merged master release 1.16 #17964
Merged master release 1.16 #17964
Conversation
Signed-off-by: Dr Nic Williams <[email protected]>
changed Kublet to Kubelet
…17329) In explanation of init container, doc says 'Initializing' pod condition. However according to doc of pod condition[1], it may be 'Initialized'. This commit fixes this misspell. [1] https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-conditions
Under `Extension Patterns` sections the link for `Flex Volume Plugins` is broken as the `flexvolume.md` file has been moved to new folder `/devel/sig-storage`. Reference commit `https://github.com/kubernetes/community/commit/ab55d850b8342abe1b87eb1c8bf397c4d05daff4`
Update content/es/docs/reference/glossary/sig.md Co-Authored-By: Rael Garcia <[email protected]> Update content/es/docs/reference/glossary/sig.md Co-Authored-By: Rael Garcia <[email protected]> Update content/es/docs/reference/glossary/sig.md Co-Authored-By: Rael Garcia <[email protected]> Update content/es/docs/reference/glossary/sig.md Co-Authored-By: Rael Garcia <[email protected]> Update content/es/docs/reference/glossary/sig.md Co-Authored-By: Rael Garcia <[email protected]> Solve YAML identation errors
Grammar errors and spelling corrections
There are many YAML manifests sneaking into the `zh/docs/` directory. These files should go to the `zh/examples` directory instead. Having these "garbage" files (not referenced anywhere) is creating confusion for the release meister when merging branches. For example, some YAML files found in the 'master' branch are no longer there in the release-1.16 branch. It is tedious, if possible at all, to solve all this kind of conflicts during a rebase. The PR cleanses the zh/docs directory for all dangling YAML files.
* First * Overview Configuration
Sometimes, pods like `coredns` only run on the master nodes. If there is a problem with upgrading the master node (e.g. if it is interrupted) those pods will not keep running - and other pods will have problems with connections. Draining the master node will switch those pods to other nodes before the upgrade-process.
* Update network-policies.md Add explanation of policy evaluation order from kubernetes/kubernetes#75435 * edit text in network-policies.md
add missing "。" by the end of 参考 card.
@daminisatya It looks like the conflict resolution broke the PR. |
@jimangel Do you have any idea on how I can fix this error?
|
That looks like an error in Chinese content, specifically: But it also looks like the most recent PR to that file (#17341) didn't change any @kubernetes/sig-docs-zh-owners ☝️ |
According to pr #17341 ,the contents of this file mysql-wordpress-persistent-volume.md should be copied directly from English. |
It looks like an extra (?) capture was added on line 427. Look at the diff of the file. Also, there may be 2X whatsnext sections. |
Keywords which can automatically close issues and at(@) mentions are not allowed in commit messages. The list of commits with invalid commit messages:
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/test-infra repository. I understand the commands that are listed here. |
Another error
|
@daminisatya , Either the file (arg to shortcode) does not exist any more or the shortcode should be changed from |
@daminisatya Just one note about this PR, you may need to also carry this PR #17976 since we need to update the HUGO_VERSION in netlify.toml as well. |
@Colstuwjx sure! |
No description provided.