Files
treasuremap/type/foundry/charts/ucp/comps/maas.yaml
T
Kaspars Skels 44d6f90a2d MAAS improvements for DNS & NodePort
Using MAAS IP for DNS allows installation by not requiring
direct internet connectivity for PXE/bootstrap interface.

NodePort usage for genesis bootstrap helps troubleshooting
during bare-metal deployment. The NodePort is unset once the
full-site (maas-scaled) is deployed.

Change-Id: I6cab0b3cfc541d43d738f3dc144bb29d848ab718
2019-09-26 10:25:58 -05:00

33 lines
787 B
YAML

---
# This file defines site-specific deviations for MaaS.
schema: armada/Chart/v1
metadata:
schema: metadata/Document/v1
name: ucp-maas
layeringDefinition:
abstract: false
layer: type
parentSelector:
name: ucp-maas-global
actions:
- method: merge
path: .
storagePolicy: cleartext
substitutions:
- src:
schema: pegleg/CommonAddresses/v1
name: common-addresses
path: .vip.maas_vip
dest:
path: .values.network.maas_ingress.addr
data:
values:
network:
region_api:
# Enable NodePort for initial genesis deployment.
# This helps with early deployment of bare-metal servers
# and is later removed by maas-scaled overrides
node_port:
enabled: true
...