Deiwin Sarjas

Could the Dockerfile for `jieyu/kind-cluster-buster:v0.1.0` be open sourced by any chance?

Oh, didn't notice that. Thank you!

Same. Happens quite often when editing projects.

Could be related to https://github.com/coredns/coredns/pull/2769 if you're using CoreDNS. Upgrading to >1.5.1 should fix the issue if that's the issue you're facing. You can further verify that that's the issue...

It seems to be still OK to upgrade. We changed `proxy` -> `forward` in the ConfigMap and added `ready` to the ConfigMap and a `readinessProbe` to the Deployment spec. ```diff...

@mogren, if that's the case, then you might want to also update some documentation. Currently [EKS docs](https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#kubernetes-1.15) refer to [Kubernetes docs](https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/), which [suggest configuring `force_tcp` for the node-local DNS cache](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/nodelocaldns/nodelocaldns.yaml#L67).

:+1:

I'm unfamiliar with the codebase. I know this may seem unrelated, but can someone please explain what's happening [here with this prompt](https://github.com/mopidy/mopidy/blob/097172d57430badd5f745f1c75b0a5a71af929c0/mopidy/local/commands.py#L45)? How does the user access stdin there?

I was able to fix by replacing `node:9.2` with `node:9.2-stretch` in my case.

> k3s has the local-storage storage class built in now: https://rancher.com/docs/k3s/latest/en/storage/ That seems to work well with `k3d create --volume ":/var/lib/rancher/k3s/storage"` for persistence. The only issue I'm seeing is that...