7 Commits (61e4ba9439638f24dae0c9e0243977eaa297ba90)

Author	SHA1	Message	Date
David McMahon	2bff72b769	Updated docs and examples for release-1.3.	2016-06-13 12:24:34 -07:00
Dawn Chen	88de86fcb9	Revert "Versioning docs and examples for v1.4.0-alpha.0." ... This reverts commit cce9db3aa9.	2016-06-10 16:46:46 -07:00
David McMahon	cce9db3aa9	Versioning docs and examples for v1.4.0-alpha.0.	2016-06-10 14:55:35 -07:00
David McMahon	dae84f5306	Update the latestReleaseBranch to release-1.2 in the munger.	2016-03-08 18:59:28 -08:00
Eric Paris	f334fc4179	Remove all docs which are moving to http://kubernetes.github.io ... All .md files now are only a pointer to where they likely are on the new site. All other files are untouched.	2016-03-04 12:49:17 -05:00
Dan Williams	6248939e11	Push responsibility for bridge-nf-call-iptables to kubelet network plugins ... bridge-nf-call-iptables appears to only be relevant when the containers are attached to a Linux bridge, which is usually the case with default Kubernetes setups, docker, and flannel. That ensures that the container traffic is actually subject to the iptables rules since it traverses a Linux bridge and bridged traffic is only subject to iptables when bridge-nf-call-iptables=1. But with other networking solutions (like openshift-sdn) that don't use Linux bridges, bridge-nf-call-iptables may not be not relevant, because iptables is invoked at other points not involving a Linux bridge. The decision to set bridge-nf-call-iptables should be influenced by networking plugins, so push the responsiblity out to them. If no network plugin is specified, fall back to the existing bridge-nf-call-iptables=1 behavior.	2016-02-23 09:34:59 -06:00
Dan Williams	fabb65c13f	Add a network plugin that duplicates "configureCBR0" functionality	2016-02-03 10:08:08 -06:00