-
Notifications
You must be signed in to change notification settings - Fork 49
oem-gce.service is not permitted to create routes in 2905.2.0 #459
Copy link
Copy link
Closed
Labels
kind/bugSomething isn't workingSomething isn't workingplatform/GCPRelated to Google Cloud PlatformRelated to Google Cloud Platform
Description
We front our kube-apiservers on GCE with a TCP load balancer. We've found that requests via the load balancer to nodes running 2905.2.0 stable are timing out.
It seems that the oem-gce service isn't permitted to create routes for eth0 that are required for ip forwarding:
Jul 29 10:31:26 master-k8s-exp-1-98sv.c.uw-dev.internal google-ip-forwarding[1468]: WARNING Non-zero exit status running ['ip', 'route', 'add', 'to', 'local', u'35.243.174.185/32', 'scope', 'host', 'dev', 'eth0', 'proto', '66']. RTNETLINK answers: Operation not permitted.
If I add --capability=CAP_NET_ADMIN to the systemd-nspawn command that runs the container then the routes are created and requests through the LB start to succeed.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugSomething isn't workingSomething isn't workingplatform/GCPRelated to Google Cloud PlatformRelated to Google Cloud Platform