* 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
* Add docs/concepts/cluster-administration/logging.md
* Add depending examples
* Translate first 2 chapters
* Coorect the path to debug/counter-pod.yaml
Only the english versions can be directly referenced.
* translate last chapter and adjust to doc style guide
* Fix french ortographic and gramatical errors
* Fix french grammar and orthograph
* Translate concepts/workloads/controllers/replicationcontroller in Korean (#15044)
* ko: Update outdated 1.14-ko.4 branch (#15099)
* Translate tasks/access-application-cluster/configure-access-multiple-clusters in Korean (#15121)
* Translate standardized glossary items in Tag Network into Korean (#15278)
* ko: Keep up with upstream - renamed files (#15030)
Co-Authored-By: Seokho <shsongist@gmail.com>
Co-Authored-By: lapee79 <lapee79@gmail.com>
Co-Authored-By: Yoon <learder@gmail.com>
Co-Authored-By: June Yi <june.yi@samsung.com>
Ubuntu 16.04.5 LTS
apt-mark unhold kubeadm && apt-get update && apt-get install -y kubeadm=1.14.x-00 && apt-mark hold kubeadm gives the below error
The following packages have unmet dependencies:
kubelet : Depends: kubernetes-cni (= 0.6.0) but 0.7.5-00 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Unholding the kubelet with kubeadm fixes the problem.
Jiacheng Xu