Skip to content

Commit

Permalink
troubleshooting-kubeadm: add guide for fixing stale CoreDNS pods (kub…
Browse files Browse the repository at this point in the history
  • Loading branch information
neolit123 authored and Mayank Kumar committed Aug 28, 2018
1 parent f21569c commit 648125b
Showing 1 changed file with 22 additions and 1 deletion.
23 changes: 22 additions & 1 deletion content/en/docs/setup/independent/troubleshooting-kubeadm.md
Original file line number Diff line number Diff line change
Expand Up @@ -238,4 +238,25 @@ EOF
)"

```
{{% /capture %}}

## `coredns` pods have `CrashLoopBackOff` or `Error` state

If you have nodes that are running SELinux with an older version of Docker you might experience a scenario
where the `coredns` pods are not starting. To solve that you can try one of the following options:

- Upgrade to a [newer version of Docker](/docs/setup/independent/install-kubeadm/#installing-docker).
- [Disable SELinux](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/security-enhanced_linux/sect-security-enhanced_linux-enabling_and_disabling_selinux-disabling_selinux).
- Modify the `coredns` deployment to set `allowPrivilegeEscalation` to `true`:

```bash
kubectl -n kube-system get deployment coredns -o yaml | \
sed 's/allowPrivilegeEscalation: false/allowPrivilegeEscalation: true/g' | \
kubectl apply -f -
```

{{< warning >}}
**Warning**: Disabling SELinux or setting `allowPrivilegeEscalation` to `true` can compromise
the security of your cluster.
{{< /warning >}}

{{% /capture %}}

0 comments on commit 648125b

Please sign in to comment.