* remove doc from kubeadm-init.md which is duplicated in kubelet-integration.md
This section in reference/setup-tools/kubeadm/kubeadm-init.md seems to significantly overlap with setup/production-environment/tools/kubeadm/kubelet-integration.md - looks like someone copy/pasted it at some point? The information in kubelet-integration.md looks more up to date than this (e.g. there actually is no `--allow-privileged=true` or `--network-plugin=cni` here?). Therefore lets delete the sections content, and have a short line linking to the other one.
If this is accepted, then #15421 is moot (because #15423 moves it to the new place).
* shorten link re. removed doc from kubeadm-init.md
as requested in https://github.com/kubernetes/website/pull/15424/ review
* drop https://kubernetes.io from link in kubeadm-init.md
* Revert "shorten link re. removed doc from kubeadm-init.md"
This reverts commit f128ce7dc2022e424a28ffc3faacb7b9a8af0ad8.
* fix bad wording
* update kubeadm-init.md based on kbhawkey review feedback
* remove duplicate sentence in kubeadm-init.md
* Adding cgroup to glossary
Adding cgroup to glossary
* Removed value from aka field
* Updating cgroups.md with cgroups changed to cgroup
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Modified cgroups to singular
* Title update and remove etc
Updated the title as mentioned in v2 docs and removed etc
* Update cgroups.md
Adding different short description
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
* Updated cgroups.md short description
* Changed file name and glossary title
* Changed the title to make it consistent
* Added Tencent Cloud Production Environment Solution
* Add an article on how to run kubernetes on Tencent Kubernetes Engine : content/en/docs/setup/production-environment/turnkey/tke.md
* Document modifications have been made as recommended by reviewer sftim. Please select this document when merging.
* Document optimization
* Modify the contents of the document : content/en/docs/setup/production-environment/turnkey/tke.md
* Add A What's Next section
* Add content: TKE is a Certified Kubernetes product.
* Add reviewers and other information.
* Delete a space
* Change information about reviewers
* Remove reviewers.
* pod-network to be done only on master node
added a note saying that Install a pod-network add on need to be done only on the master node
* updated where to run pod-network doc
All admission control plugins support two modes for specifying their
configuration: linking to an external file using the `path` key in the
shared admission configuration file, or directly embedding the
configuration using the `configuration` key in the shared admission
configuration file.
This commit makes the ImagePolicyWebhook documentation mention the
embedded configuration option.
* New getting started blog post
I'd like to submit a blog post for the kubernetes.io blog targeted to people just getting started with Kubernetes. I myself am still new to it but want to start writing more to share what I am learning and help others along the way. My point of view is a little different than most people who post on the kubernetes.io blog since I am an independent consultant and I also work mostly with Microsoft products - so some of my resources are from Microsoft which seems rare for some reason in most Kubernetes blog posts I find on the web.
* Added the images and changed md for path
I added the image files and changed the paths in the markdown to /static/images/blog/...
* fix path
* Added date to header
Added a date to get it on netlify preview
* made changes
* Update and rename get-started-with-kubernetes-using-python.md to 2019-07-23-get-started-with-kubernetes-using-python.md
When upgrading controlplane nodes, upgrading the kubelets should be done
as the last step after "kubeadm upgrade" was run on all of the control
plane nodes already.
Also apply consistency related cleanup to sections and section names.
I changed a question that had no question mark into a statement. I also changed the heading from the first person to the second person, because the topic it treats the reader as the second person everywhere else.
* Switch to "failure zone" term
Previous wording, "availability zone", is specific to certain cloud
service providers (eg AWS).
* Refer to glossary terms where appropriate
* Reword signposting to examples
* Assign stable name to anchor
* Link to standard node labels
* Fix incorrect feature state claims
* NodeRestriction admission plugin needs Kubernetes v1.11
(or later)
* Move further reading to whatsnext section
* Fix link to cluster setup
* Drop advice about older kubectl
Kubernetes v1.14+ definitely does offer a compatible kubectl
* Drop outdated comment about downloading examples
* Call an availability zone an availability zone
* Improve init containers page
- Overall rewording
- Link to “Debug init containers” in whatsnext
- Explain terms / use glossary references
- Use glossary shortcodes where appropriate
- Expand terms like QoS and cgroup that aren't in the glossary
- Only document & recommend stable syntax
- Tweak initContainer examples to use project style
- Drop vestigialreference to StatefulSet
Also: write “container” in lower case
Most of the places where this page talks about containers, it's as a
concept rather than an object in the Kubernetes API. Adjust case
accordingly.
* Reword what's next section
Neha Gupta