Hi Dhanashree. Thanks for writing. I wish I could give you a detailed explanation, but I know very little about how OpenShift sets up networking. The docker0 bridge is the one docker installs by default, and the one I used to illustrate the simple container networking scenario in my post. If you run any docker containers locally you should see the eth0 virtual adapter in the container connected through a TUN/TAP interface to docker0. There are other ways this can be set up. For example Docker Compose creates a separate bridge for each compose app that you run. According to the documentation for OpenShift br0 should be the bridge it is using for containers, but I can’t say why it is in a down state when you observed it. Perhaps this will help: https://blog.avinetworks.com/tech/kubernetes-and-openshift-networking-primer. Lastly, traceroute won’t work for a cluster IP because it relies on icmp packets and the netfilter rules that make service networking function don’t forward icmp as far as I know.
