![]() This is problematic in aīunch of ways for GCE, so the whole thing needs to be optional. Reply to this email directly or view it on GitHub.Ĭatching up on older issues that have languished. ![]() I just don't see the point of the mac management here since they won't (likely? probably?) be exposed/visible outside. (at least the CoreOS example kube setup does leak the pod MAC out to the infrastructure, so I guess some people do it.) Pod IPs are much more likely to leak out into the underlying infrastructure, but you claim no need to systemically manage them from the outside. So the hosting infrastructure never sees them. Would rather fill the MAC with meaningful info rather than random info. Is that true? I had assumed they would occasionally escape, so being able to say "oh hey, that darn pod djeickektnejciekt escaped its bounds again" or "why are all those packets coming from Kubernetes that cleverly have the MAC prefix DEADBEEF" would be somewhat useful. Pod MAC addresses exist only inside the cluster and (likely? hopefully?) only in an overlay network. It's a question of usefulness in my mind. On Nov 11, 2014, at 5:24 PM, Eric Paris wrote:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |