diff options
author | 2018-07-06 09:00:32 +0000 | |
---|---|---|
committer | 2018-07-06 09:00:32 +0000 | |
commit | 2e26069ab117f843804280519c99fdd8708a4cf4 (patch) | |
tree | ced2920948917dc6e1d8435112fcc78363f13a5c /docs/_static | |
parent | 2e1062e7e162dae9c3ff29404a0a365b36baf958 (diff) |
Update git submodules
* Update docs/submodules/yardstick from branch 'master'
- Merge "Specify the networks to be used per pod"
- Specify the networks to be used per pod
If CRD "Network" is defined and network items are created, each pod (server)
can have access to one or several networks. This is defined in the metadata
section, as "annotations.networks" [1].
Example of Kubernetes pod definition with networks:
apiVersion: v1
kind: Pod
metadata:
name: test-pod
annotations:
networks: '[{"name": "flannel"}]'
Example of Yardstick server definition with networks:
context:
type: Kubernetes
servers:
host:
containers:
- name: ...
networks:
- flannel # These names must be defined in
# context.networks
...
networks:
- name: flannel
plugin: flannel
Kubernetes annotations [2].
[1]https://github.com/intel/multus-cni/tree/b9446232cdf4f1b6f2bea583291973cc97e963f4#configuring-multus-to-use-kubeconfig-and-a-default-network
[2]https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
JIRA: YARDSTICK-1178
Change-Id: I6e7b4bacf10810833ec733c14d44e5db613675e3
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
Diffstat (limited to 'docs/_static')
0 files changed, 0 insertions, 0 deletions