whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove swagger-ui link, fix page.version variable (#3185)

Browse Source 
* Remove swagger-ui link, fix page.version variable

* remove swagger-ui redirect

* use 2 decimal version for cluster-large.md

* fix swagger-ui message

* replace URL w/ final destination

* address feedback

* add link to swagger.json at https://github.com/kubernetes/kubernetes/blob/master/api/openapi-spec/swagger.json

* remove redundant sentence
This commit is contained in:
Andrew Chen
2017-04-03 01:13:10 -07:00
committed by GitHub
parent 9b5e8bac46
commit 6ed0c34d2a
9 changed files with 8 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/cluster-administration/network-plugins.md
+1 -1
View File
@@ -25,7 +25,7 @@ The kubelet has a single default network plugin, and a default network common to
## Network Plugin Requirements
Besides providing the [`NetworkPlugin` interface](https://github.com/kubernetes/kubernetes/tree/{{page.version}}/pkg/kubelet/network/plugins.go) to configure and clean up pod networking, the plugin may also need specific support for kube-proxy. The iptables proxy obviously depends on iptables, and the plugin may need to ensure that container traffic is made available to iptables. For example, if the plugin connects containers to a Linux bridge, the plugin must set the `net/bridge/bridge-nf-call-iptables` sysctl to `1` to ensure that the iptables proxy functions correctly. If the plugin does not use a Linux bridge (but instead something like Open vSwitch or some other mechanism) it should ensure container traffic is appropriately routed for the proxy.
Besides providing the [`NetworkPlugin` interface](https://github.com/kubernetes/kubernetes/tree/{{page.fullversion}}/pkg/kubelet/network/plugins.go) to configure and clean up pod networking, the plugin may also need specific support for kube-proxy. The iptables proxy obviously depends on iptables, and the plugin may need to ensure that container traffic is made available to iptables. For example, if the plugin connects containers to a Linux bridge, the plugin must set the `net/bridge/bridge-nf-call-iptables` sysctl to `1` to ensure that the iptables proxy functions correctly. If the plugin does not use a Linux bridge (but instead something like Open vSwitch or some other mechanism) it should ensure container traffic is appropriately routed for the proxy.
By default if no kubelet network plugin is specified, the `noop` plugin is used, which sets `net/bridge/bridge-nf-call-iptables=1` to ensure simple configurations (like docker with a bridge) work correctly with the iptables proxy.