Skip to content

Commit

Permalink
Update outdated l10n(ko) contents (#10915)
Browse files Browse the repository at this point in the history
fixes #10904
  • Loading branch information
gochist authored and k8s-ci-robot committed Nov 8, 2018
1 parent ecef1e7 commit 6fc6bbb
Show file tree
Hide file tree
Showing 5 changed files with 10 additions and 5 deletions.
1 change: 0 additions & 1 deletion content/ko/docs/concepts/overview/kubernetes-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,6 @@ API에 원격 접속하는 방법은 [Controlling API Access doc](/docs/referenc

{{% /capture %}}

{{< toc >}}

{{% capture body %}}

Expand Down
2 changes: 1 addition & 1 deletion content/ko/docs/home/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ cid: userJourneys
css: /css/style_user_journeys.css
js: /js/user-journeys/home.js, https://use.fontawesome.com/4bcc658a89.js
display_browse_numbers: true
linkTitle: "문서"
linkTitle: ""
main_menu: true
weight: 10
menu:
Expand Down
6 changes: 5 additions & 1 deletion content/ko/docs/setup/independent/troubleshooting-kubeadm.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ This may be caused by a number of problems. The most common are:

There are two common ways to fix the cgroup driver problem:

1. Install docker again following instructions
1. Install Docker again following instructions
[here](/docs/setup/independent/install-kubeadm/#installing-docker).
1. Change the kubelet config to match the Docker cgroup driver manually, you can refer to
[Configure cgroup driver used by kubelet on Master Node](/docs/setup/independent/install-kubeadm/#configure-cgroup-driver-used-by-kubelet-on-master-node)
Expand Down Expand Up @@ -104,6 +104,10 @@ Right after `kubeadm init` there should not be any pods in these states.
likely that the Pod Network solution that you installed is somehow broken. You
might have to grant it more RBAC privileges or use a newer version. Please file
an issue in the Pod Network providers' issue tracker and get the issue triaged there.
- If you install a version of Docker older than 1.12.1, remove the `MountFlags=slave` option
when booting `dockerd` with `systemd` and restart `docker`. You can see the MountFlags in `/usr/lib/systemd/system/docker.service`.
MountFlags can interfere with volumes mounted by Kubernetes, and put the Pods in `CrashLoopBackOff` state.
The error happens when Kubernetes does not find `var/run/secrets/kubernetes.io/serviceaccount` files.

## `coredns` (or `kube-dns`) is stuck in the `Pending` state

Expand Down
2 changes: 1 addition & 1 deletion content/ko/docs/setup/multiple-zones.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ There are some important limitations of the multizone support:

* We assume that the different zones are located close to each other in the
network, so we don't perform any zone-aware routing. In particular, traffic
that goes via services might cross zones (even if pods in some pods backing that service
that goes via services might cross zones (even if some pods backing that service
exist in the same zone as the client), and this may incur additional latency and cost.

* Volume zone-affinity will only work with a `PersistentVolume`, and will not
Expand Down
4 changes: 3 additions & 1 deletion content/ko/docs/setup/pick-right-solution.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ a Kubernetes cluster from scratch.

## 로컬 머신 솔루션

* [Minikube](/docs/setup/minikube/) is the recommended method for creating a local, single-node Kubernetes cluster for development and testing. Setup is completely automated and doesn't require a cloud provider account.
* [Minikube](/docs/setup/minikube/) is a method for creating a local, single-node Kubernetes cluster for development and testing. Setup is completely automated and doesn't require a cloud provider account.

* [microk8s](https://microk8s.io/) provides a single command installation of the latest Kubernetes release on a local machine for development and testing. Setup is quick, fast (~30 sec) and supports many plugins including Istio with a single command.

Expand Down Expand Up @@ -158,6 +158,7 @@ These solutions are combinations of cloud providers and operating systems not co
### 베어 메탈

* [CoreOS](/docs/setup/custom-cloud/coreos/)
* [Digital Rebar](/docs/setup/on-premises-metal/krib/)
* [Fedora (Single Node)](/docs/getting-started-guides/fedora/fedora_manual_config/)
* [Fedora (Multi Node)](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)
* [Kubernetes on Ubuntu](/docs/getting-started-guides/ubuntu/)
Expand Down Expand Up @@ -219,6 +220,7 @@ any | [Gardener Cluster-Operator](https://kubernetes.io/blog/20
Alibaba Cloud Container Service For Kubernetes | ROS | CentOS | flannel/Terway | [docs](https://www.aliyun.com/product/containerservice) | Commercial
Agile Stacks | Terraform | CoreOS | multi-support | [docs](https://www.agilestacks.com/products/kubernetes) | Commercial
IBM Cloud Kubernetes Service | | Ubuntu | calico | [docs](https://console.bluemix.net/docs/containers/container_index.html) | Commercial
Digital Rebar | kubeadm | any | metal | [docs](/docs/setup/on-premises-metal/krib/) | Community ([@digitalrebar](https://github.com/digitalrebar))


{{< note >}}
Expand Down

0 comments on commit 6fc6bbb

Please sign in to comment.