Is K8s Too Complicated? ￼
Ok, I&#x27;ll bite.<p>I posted this in another thread, but check this out: <a href="https:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;50195896&#x2F;how-do-i-get-one-pod-to-network-to-another-pod-in-kubernetes-simple" rel="nofollow">https:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;50195896&#x2F;how-do-i-get-on...</a>. That&#x27;s the amount of crap I waded through trying to rubber-ducky myself into figuring out how to get two pods to talk to each other. In the end, I copied a solution my friend had gotten, and it&#x27;s still not great. I&#x27;d love to be able to use Ingress or Calico or Fabric or <i></i>something<i></i> to get path routing to work in Kubernetes, but unfortunately all the examples I&#x27;ve seen online suffer from too much specificity. Which is the Kubernetes problem - it can do everything so trying to get it to do the <i>one</i> thing you want is hard.<p>Here is the kubernetes cluster I ended up building. If anyone has any ideas on how to add path routing let me know - <a href="https:&#x2F;&#x2F;github.com&#x2F;patientplatypus&#x2F;KubernetesMultiPodCommunication" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;patientplatypus&#x2F;KubernetesMultiPodCommuni...</a>