@@ -138,10 +138,10 @@ Right after `kubeadm init` there should not be any pods in these states.
138138
139139- If there are pods in one of these states _right after_ `kubeadm init`, please open an
140140 issue in the kubeadm repo. `coredns` (or `kube-dns`) should be in the `Pending` state
141- until you have deployed the network solution .
141+ until you have deployed the network add-on .
142142- If you see Pods in the `RunContainerError`, `CrashLoopBackOff` or `Error` state
143- after deploying the network solution and nothing happens to `coredns` (or `kube-dns`),
144- it's very likely that the Pod Network solution that you installed is somehow broken.
143+ after deploying the network add-on and nothing happens to `coredns` (or `kube-dns`),
144+ it's very likely that the Pod Network add-on that you installed is somehow broken.
145145 You might have to grant it more RBAC privileges or use a newer version. Please file
146146 an issue in the Pod Network providers' issue tracker and get the issue triaged there.
147147- If you install a version of Docker older than 1.12.1, remove the `MountFlags=slave` option
@@ -152,14 +152,14 @@ Right after `kubeadm init` there should not be any pods in these states.
152152# # `coredns` (or `kube-dns`) is stuck in the `Pending` state
153153
154154This is **expected** and part of the design. kubeadm is network provider-agnostic, so the admin
155- should [install the pod network solution ](/docs/concepts/cluster-administration/addons/)
155+ should [install the pod network add-on ](/docs/concepts/cluster-administration/addons/)
156156of choice. You have to install a Pod Network
157157before CoreDNS may be deployed fully. Hence the `Pending` state before the network is set up.
158158
159159# # `HostPort` services do not work
160160
161161The `HostPort` and `HostIP` functionality is available depending on your Pod Network
162- provider. Please contact the author of the Pod Network solution to find out whether
162+ provider. Please contact the author of the Pod Network add-on to find out whether
163163` HostPort` and `HostIP` functionality are available.
164164
165165Calico, Canal, and Flannel CNI providers are verified to support HostPort.
0 commit comments