Skip to content
This repository has been archived by the owner on Nov 9, 2021. It is now read-only.

coredns gets killed by oom #45

Open
chrifey opened this issue Dec 16, 2018 · 1 comment
Open

coredns gets killed by oom #45

chrifey opened this issue Dec 16, 2018 · 1 comment
Assignees
Labels
invalid This doesn't seem right stale Things needing work or comment but haven't been touched in a while

Comments

@chrifey
Copy link

chrifey commented Dec 16, 2018

I deployed a cluster with 3 nodes (master + 2 worker nodes).

After the deployment is finished, the cluster is fine, but when I schedule services, the two coredns pods get killed from out-of-memory (oom). That makes coredns going into a crash-loop.

I'm not sure, whether this I a config problem on my side, but I fixed it with using kube-dns [1] instead of coredns by passing --feature-gates=CoreDNS=false.

[1] https://kubernetes.io/docs/tasks/administer-cluster/coredns/#installing-kube-dns-instead-of-coredns-with-kubeadm

Docker Version: 18.04.0-ce
K8s: v1.11.4

@chris-short chris-short self-assigned this Dec 8, 2019
@chris-short chris-short added the invalid This doesn't seem right label Dec 8, 2019
@chris-short
Copy link
Owner

Is this still an issue?

@chris-short chris-short added the stale Things needing work or comment but haven't been touched in a while label Dec 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
invalid This doesn't seem right stale Things needing work or comment but haven't been touched in a while
Projects
None yet
Development

No branches or pull requests

2 participants