are not happy with it • Too many annotations, most are not portable In 2018 we expect more from an L7 proxy! Was a hot topic at KubeCon 2017, much conflicting input, still not resolved Exploring alternate models, APIs, ideas
alpha now (needs CI) Dual-stack KEP is ~done Requires some significant changes • Multiple IPs for a single Pod (API change) • Multiple IPs for a single Service->Endpoint (API change) • Kube-proxy to run multiple modes • Kubelet to handle Pod hostPorts Could use more dev/test help!
same-node Services Stalled for a while to investigate holistically After exploring, the simplest option seems sufficient (yay!) Some tricky corner-cases and scalability concerns Aiming for a limited alpha in 1.14
organically” • Kind of a grab-bag of features (aka “a disaster”) • Hard to use • Doesn’t scale well Need to start segmenting the “core” API group Opportunity to rethink and refactor • Endpoints -> Endpoint • Split the grouping construct from the input mechanisms • Maybe EOL some troublesome features
don’t Not clear which do or don’t Not all of them perform equally well Not clear what it means to multicast in k8s (e.g. what about namespaces?) KEP in progress to define behavior, but has to stay optional
around versions and feature support Some changes happening in kube-proxy to reach max parity Some incompatibilities in name resolution (e.g. search path) Some things just aren’t possible (e.g. hostNetwork)
A Pod can be in multiple networks at once Caution to not repeat old mistakes - keep it simple Interesting intersection with devices, e.g. SRIOV SIG-Network Plumbing WG has a spec, (built on CNI) and impl (multus)