mirror of https://github.com/kubernetes/kops.git
WIP network mode docs
This commit is contained in:
parent
2f4ac90661
commit
d2ccc99e86
|
@ -20,4 +20,38 @@ kops currently supports 3 networking modes:
|
|||
* `kubenet` kubernetes native networking via a CNI plugin. Also has less reliance on Docker's networking.
|
||||
* `external` networking is done via a Daemonset
|
||||
|
||||
TODO: Explain the difference between pod networking & inter-pod networking.
|
||||
TODO: Explain the difference between pod networking & inter-pod networking.
|
||||
|
||||
|
||||
|
||||
## Switching between networking providers
|
||||
|
||||
Make sure you are running the latest kops: `git pull && make`. `kops version` should be `Version git-2f4ac90`
|
||||
|
||||
`kops edit cluster` and you should see a block like:
|
||||
|
||||
```
|
||||
networking:
|
||||
classic: {}
|
||||
```
|
||||
|
||||
That means you are running with `classic` networking. The `{}` means there are no configuration options
|
||||
(but we have to put something in there so that we do choose classic).
|
||||
|
||||
To switch to kubenet, edit to be:
|
||||
```
|
||||
networking:
|
||||
kubenet: {}
|
||||
```
|
||||
|
||||
Now follow the normal update / rolling-update procedure:
|
||||
|
||||
* `kops update cluster` to preview
|
||||
* `kops update cluster --yes` to apply
|
||||
* `kops rolling-update cluster` to preview the rolling-update
|
||||
* `kops rolling-update cluster --yes` to roll all your instances
|
||||
|
||||
Your cluster should be ready in a few minutes.
|
||||
|
||||
It is not trivial to see that this has worked; the easiest way seems to be to SSH to the master and verify
|
||||
that kubelet has been run with `--network-plugin=kubenet`
|
Loading…
Reference in New Issue