In our last post we talked about an important Kubernetes networking construct – the service. Services provide a means for pods running within the cluster to find other pods and also provide rudimentary load balancing capabilities. We saw that services can create DNS entries within Kube-DNS which makes the service accessible by name as well. So now that we know how you can use services to access pods within the cluster it seems prudent to talk about how things outside of the cluster can access these same services. It might make sense to use the same service construct to provide this functionality, but recall that the services are assigned IP addresses that are only known to the cluster. In reality, the service CIDR isnt actually routed anywhere but the Kubernetes nodes know how to interact with service IPs because of the netfilter rules programmed by the kube-proxy. The service network just needs to be unique so that the containers running in the pod will follow their default route out to the host where the netfilter rules will come into play. So really the service network is sort of non-existent from a routing perspective as it’s only locally significant to each host. Continue reading
The post Worth Reading: Password and security recommendations appeared first on rule 11 reader.
Every day operation of a Cisco router is likely to cause failure.
The post 9 Easy Ways to Break a Cisco Network appeared first on EtherealMind.
From an atomic museum to a sci-fi center, Vegas has lots of nerdy attractions.
Some background on the Free Range Routing project.
The post Response: Why a new routing stack? – Russ White appeared first on EtherealMind.