forked from sassoftware/viya4-deployment
-
Notifications
You must be signed in to change notification settings - Fork 0
/
ansible-vars-iac.yaml
44 lines (33 loc) · 1.16 KB
/
ansible-vars-iac.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
## Cluster
NAMESPACE: <namespace>
## MISC
DEPLOY: true # Set to false to stop at generating the manifest
LOADBALANCER_SOURCE_RANGES: ['<desired_cidr_blocks>']
## Storage
V4_CFG_MANAGE_STORAGE: true
## SAS API Access
V4_CFG_SAS_API_KEY: '<api_client_id>'
V4_CFG_SAS_API_SECRET: '<api_client_secret>'
V4_CFG_ORDER_NUMBER: <order_number>
## CR Access
V4_CFG_CR_USER: <container_registry_user>
V4_CFG_CR_PASSWORD: <container_registry_password>
## Ingress
V4_CFG_INGRESS_TYPE: ingress
V4_CFG_INGRESS_FQDN: <desired_fqdn>
V4_CFG_TLS_MODE: "full-stack" # [full-stack|front-door|ingress-only|disabled]
## Postgres
## LDAP
V4_CFG_EMBEDDED_LDAP_ENABLE: true
## Consul UI
V4_CFG_CONSUL_ENABLE_LOADBALANCER: false
## SAS/CONNECT
V4_CFG_CONNECT_ENABLE_LOADBALANCER: false
## Monitoring and Logging
## uncomment and update the below values when deploying the viya4-monitoring-kubernetes stack
#V4M_BASE_DOMAIN: <base_domain>
## Viya Start and Stop Schedule
## uncomment and update the values below with CronJob schedule expressions if you would
## like to start and stop your Viya Deployment on a schedule
#V4_CFG_VIYA_START_SCHEDULE: "0 7 * * 1-5"
#V4_CFG_VIYA_STOP_SCHEDULE: "0 19 * * 1-5"