vino/config/samples/vino_cr_4_workers_1_cp.yaml
Kostiantyn Kalynovskyi 5d70de0f3d Generate bootMAC and change boot network to NAT
Change-Id: Id8776e8153c57682ed02f4e6534d8dfda4ed25a1
2021-06-03 20:24:12 +00:00

56 lines
1.5 KiB
YAML

apiVersion: airship.airshipit.org/v1
kind: Vino
metadata:
name: vino-test-cr
labels: {}
spec:
vmBridge: vm-infra
nodeLabelKeysToCopy:
- "airshipit.org/server"
- "airshipit.org/rack"
nodeSelector:
matchLabels:
beta.kubernetes.io/os: linux
configuration:
cpuExclude: 0-1
networks:
- name: vm-infra
subnet: 192.168.2.0/20
type: ipv4
allocationStart: 192.168.2.10
allocationStop: 192.168.2.14 # docs should specify that the range should = number of vms (to permit future expansion over multiple vino crs etc)
routes:
- network: 10.0.0.0
netmask: 255.255.255.0
gateway: $vinobridge # vino will need to populate this from the nodelabel value `airshipit.org/vino.nodebridgegw`
dns_servers: ["135.188.34.124"]
macPrefix: "52:54:00:06:00:00"
nodes:
- name: master
count: 1
bmhLabels:
airshipit.org/k8s-role: master
networkDataTemplate:
name: "test-template"
namespace: "default"
networkInterfaces:
- name: management
type: network
network: vm-infra
mtu: 1500
- name: worker
count: 4
bmhLabels:
airshipit.org/k8s-role: worker
networkDataTemplate:
name: "test-template"
namespace: "default"
networkInterfaces:
- name: management
type: network
network: vm-infra
mtu: 1500
bmcCredentials:
username: admin
password: passw0rd