vino/config/samples/vino_cr.yaml
Kostiantyn Kalynovskyi eda3300093 Add BMH credentials support
With this change there will be only one supported credential per
VINO CR. Since the CR is mounted inside the sushy tools container,
sushy startup script can access these credentials and set up
authentication. This approach allows to get basic functionality
working, in the future, we would probably want to hide these
credentials in a secret so they can't be seen in plain text from
VINO CR.

Change-Id: I4aa2fb1ee1f5633b889acfa901283f5fa51ad2c1
2021-03-01 16:30:21 +00:00

41 lines
1.1 KiB
YAML

apiVersion: airship.airshipit.org/v1
kind: Vino
metadata:
name: vino-test-cr
# labels: ...
spec:
nodeSelector:
matchLabels:
beta.kubernetes.io/os: linux
configuration:
cpuExclude: 0-4,54-60
redfishCredentialSecret:
name: redfishSecret
networks:
- name: management
subnet: 192.168.2.0/20
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:
- to: 10.0.0.0/24
via: $vino.nodebridgegw # vino will need to populate this from the nodelabel value `airshipit.org/vino.nodebridgegw`
dns_servers: ["135.188.34.124"]
- name: external
subnet: 169.0.0.0/24
routes:
- to: 0.0.0.0/0
via: 169.0.0.1
allocationStart: 169.0.0.10
allocationStop: 169.0.0.254
vmBridge: lo
nodes:
- name: "worker"
count: 3
networkDataTemplate:
name: "test-template"
namespace: "default"
bmcCredentials:
username: "admin"
password: "passw0rd"