Red Hat Bugzilla – Bug 1308701
Kubelet proxy must be able to run in userspace and iptables mode
Last modified: 2016-05-31 04:57:47 EDT
Description of problem:
The kubelet proxy changed from userspace mode to iptables mode. There must be a way to opt back into userspace-mode proxy.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The node starts in iptables mode by default, or can be explicitly set in the node-config.yaml with:
To start in userspace proxy mode, set this in node-config.yaml:
We need to verify that the SDN works as expected, and that the node indicates in the start up logs that userspace or iptables mode is being used according to the proxy config
Fixed in origin in https://github.com/openshift/origin/pull/7088
Fixed in OSE in https://github.com/openshift/ose/pull/138
Verified with OSE 3.1 Errata build 2016-02-16.1
The kube-proxy can be configured to work as userspace or iptables now by editing the node-config.yaml.
And the SDN related features keep working fine.
But I have a question, when I set the loglevel > 4, eg, --loglevel=5, the new added logs will not be found in the node log.
glog.V(0).Info("Using iptables Proxier.")
glog.Infof("Started Kubernetes Proxy on %s", c.ProxyConfig.BindAddress.String())
If I set the loglevel =< 4, then it would be ok.
@Jordan Do you know why some of the logs are missing when there is a higher loglevel?
no idea on the --loglevel issue
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.