[docs][minor] Typos and formatting for default network annotation docs

This commit is contained in:
dougbtv
2019-01-07 11:18:08 -05:00
parent 1558896125
commit 0d8296c54c

View File

@@ -250,9 +250,9 @@ samplepod 1/1 Running 0 31s
Users may also specify the default network for any given pod (via annotation), for cases where there are multiple cluster networks available within a Kubernetes cluster.
The possible use cases could be, for example:
Example use cases may include:
1. During default network migration (e.g. from Flannel to Calico), it maybe be practical if both network solutions are able to operate in parallel. Users can then control which network a pod should attach to during the transition period.
1. During a migration from one default network to another (e.g. from Flannel to Calico), it may be practical if both network solutions are able to operate in parallel. Users can then control which network a pod should attach to during the transition period.
2. Some users may deploy multiple cluster networks for the sake of their security considerations, and may desire to specify the default network for individual pods.
Follow these steps to specify the default network on a pod-by-pod basis:
@@ -261,12 +261,12 @@ Follow these steps to specify the default network on a pod-by-pod basis:
2. Next, you can specify the network you want in pods with the `v1.multus-cni.io/default-network` annotation. Pods which do not specify this annotation will keep using the CNI as defined in the Multus config file.
```yaml
apiVersion: v1
kind: Pod
metadata:
name: pod-example
annotations:
v1.multus-cni.io/default-network: calico-conf
...
```
```yaml
apiVersion: v1
kind: Pod
metadata:
name: pod-example
annotations:
v1.multus-cni.io/default-network: calico-conf
...
```