Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
@tjm problem might be that DO cluster comes automatically with preloaded kube-proxy. Right after cluster initialization we installed flannel and our network between nodes did not work.
I think that, you need to uninstall kube-proxy, if you prefer Flannel.
I can no longer edit my post, but apparently I misunderstood how the k8s service subnet works… It is not meant to respond to ICMP requests so “ping 10.245.0.10” is expected to fail and the subnet that kube-dns lives on is not meant to match the pod subnet.
However, I have done some more testing and apparently pods running on one of my nodes can hit kube-dns, but pods on the other node cannot. This the case regardless of which node kube-dns is present on. I suspect there is a problem with that node’s configuration, so I will try recycling it and see what happens…
Hi @tjm
Did you get flannel to work? We are trying to configure flannel on DO cluster without any success.