?i&lressem,nayul,?k&eelf-no,orgn,relc,?le&crev,napysae,?maerdepyt,n&aecolatigidno,evia,?opxe:.gnigats,,poon,r&cne:.dnetnorf,,emarf,ubaez,?s&jasudem,serpirots,?t&ayn,i&belet,l&maerts,per:.di,,??luavreve.yaler,xenw,?wolfrettulf,xevnoc,y&awliar.pu,f&ilten,ten,????ra&a?hs??u&ekam?llag?org!.esruocsid,cts?kouk?nayalo???vsr?xece4ibgm--nx??q&a!3a9y--nx??g?i!.&gro?lim?moc?ten?ude?vog???m?se??r&a!.&a&cisum?sanes??bog?g&es?ro??l&autum?im??moc?pooc?rut?t&e&b?n??ni??ude?vog??4d5a4prebgm--nx?b?c?eydoog?los?t&...

- Added support to the kube-proxy nodePortAddresses / --nodeport-addresses option to
  accept the value "primary", meaning to only listen for NodePort connections
  on the node's primary IPv4 and/or IPv6 address (according to the Node object).
  This is strongly recommended, if you were not previously using
  --nodeport-addresses, to avoid surprising behavior.