fix: added ansible vars sample

Author: Abhishek Kumar

examples/ansible-vars-gateway-api-envoy.yaml

@@ -0,0 +1,54 @@
+---
+## Cluster
+PROVIDER: <provider> # [azure|aws|gcp|custom]
+CLUSTER_NAME: <cluster_name>
+NAMESPACE: <viya_namespace>
+
+## MISC
+DEPLOY: true
+LOADBALANCER_SOURCE_RANGES: [<desired_cidr_blocks>]
+
+## SAS API Access
+V4_CFG_APIM_CLIENT_ID: <apim_client_id>
+V4_CFG_APIM_CLIENT_SECRET: <apim_client_secret>
+V4_CFG_ORDER_NUMBER: <order_number>
+V4_CFG_CADENCE_NAME: <cadence_name> # [lts|stable]
+V4_CFG_CADENCE_VERSION: <cadence_version>
+
+## CR Access
+V4_CFG_CR_USER: <container_registry_user>
+V4_CFG_CR_PASSWORD: <container_registry_password>
+
+## Ingress / TLS
+V4_CFG_INGRESS_TYPE: envoy-gateway
+V4_CFG_INGRESS_MODE: private # set public only if required
+V4_CFG_TLS_MODE: full-stack # [full-stack|front-door|ingress-only|disabled]
+V4_CFG_INGRESS_FQDN: aksgw.unx.sas.com
+V4_CFG_BASE_DOMAIN: viya4.aksgw.unx.sas.com
+
+## Install Gateway API + Envoy Gateway in baseline
+V4_CFG_INSTALL_GATEWAY_API: true
+V4_CFG_INSTALL_ENVOY_GATEWAY: true
+ENVOY_GATEWAY_GATEWAYCLASS_NAME: envoy
+V4_CFG_VIYA_GATEWAY_CLASS_NAME: envoy
+
+## Baseline shared Gateway (parent for ListenerSet)
+V4_CFG_BASELINE_CREATE_BOOTSTRAP_GATEWAY: true
+V4_CFG_BASELINE_GATEWAY_NAMESPACE: gw-system
+V4_CFG_BASELINE_GATEWAY_NAME: k8s-gw
+V4_CFG_BASELINE_GATEWAY_ENABLE_HTTP_LISTENER: true
+V4_CFG_BASELINE_GATEWAY_TLS_SECRET_NAME: gateway-secret
+
+## Generate Gateway API resources for viya flow
+V4_CFG_GENERATE_GATEWAY_API_RESOURCES: true
+
+## ListenerSet name in viya namespace (optional override)
+# V4_CFG_VIYA_LISTENERSET_NAME: "{{ NAMESPACE }}-listeners"
+
+## Do not set V4_CFG_VIYA_GATEWAY_NAMESPACE/V4_CFG_VIYA_GATEWAY_NAME
+## for envoy-gateway mode unless you intentionally want extra secret sync behavior.
+
+## Optional runtime toggles
+# V4_CFG_VIYA_HTTPROUTE_AUTO_DISCOVER: true
+# GATEWAY_API_VERSION: v1.5.0
+# GATEWAY_API_NAMESPACE_LABEL_MODE: experimental

examples/ansible-vars-iac.yaml

@@ -26,14 +26,6 @@ V4_CFG_INGRESS_TYPE: contour
 V4_CFG_INGRESS_FQDN: <desired_fqdn>
 V4_CFG_TLS_MODE: full-stack # [full-stack|front-door|ingress-only|disabled]
 
-## Optional Gateway API + Envoy Gateway
-V4_CFG_INSTALL_GATEWAY_API: false
-V4_CFG_INSTALL_ENVOY_GATEWAY: false
-V4_CFG_GENERATE_GATEWAY_API_RESOURCES: false
-# V4_CFG_VIYA_GATEWAY_CLASS_NAME: envoy
-# V4_CFG_VIYA_HTTPROUTE_BACKEND_SERVICE: <viya_backend_service_name>
-# V4_CFG_VIYA_HTTPROUTE_BACKEND_PORT: 80
-
 ## Postgres
 
 ## LDAP
@@ -49,4 +41,4 @@ V4_CFG_CONNECT_ENABLE_LOADBALANCER: false
 ## 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"
+# V4_CFG_VIYA_STOP_SCHEDULE: "0 19 * * 1-5"

examples/ansible-vars-multi-zone.yaml

@@ -82,6 +82,7 @@ V4_CFG_MULTI_ZONE_OPENDISTRO_ENABLED: true           # Search/logging
 V4_CFG_MULTI_ZONE_WORKLOAD_ORCHESTRATOR_ENABLED: true # Job scheduling
 V4_CFG_MULTI_ZONE_DATA_AGENT_ENABLED: true           # Data services
 V4_CFG_MULTI_ZONE_STATELESS_ENABLED: true            # Stateless services (Deployments)
+V4_CFG_MULTI_ZONE_CONTOUR_ENABLED: true              # Contour ingress controller HA (replicaCount=detected zones, min=2 + zone spread)
 
 # Advanced options
 V4_CFG_SINGLE_ZONE_FALLBACK: true          # Handle single-zone clusters gracefully
@@ -135,4 +136,4 @@ V4_CFG_POSTGRES_SERVERS:
 # 1. Check node labels: kubectl get nodes --show-labels
 # 2. Verify zone distribution: kubectl get nodes -L topology.kubernetes.io/zone
 # 3. Check StatefulSet events: kubectl describe statefulset <name> -n <namespace>
-# 4. Temporarily disable multi-zone: V4_CFG_MULTI_ZONE_ENABLED: false
+# 4. Temporarily disable multi-zone: V4_CFG_MULTI_ZONE_ENABLED: false

examples/ansible-vars.yaml

@@ -37,14 +37,6 @@ V4_CFG_INGRESS_TYPE: contour
 V4_CFG_INGRESS_FQDN: <desired_fqdn>
 V4_CFG_TLS_MODE: full-stack # [full-stack|front-door|ingress-only|disabled]
 
-## Optional Gateway API + Envoy Gateway
-V4_CFG_INSTALL_GATEWAY_API: false
-V4_CFG_INSTALL_ENVOY_GATEWAY: false
-V4_CFG_GENERATE_GATEWAY_API_RESOURCES: false
-# V4_CFG_VIYA_GATEWAY_CLASS_NAME: envoy
-# V4_CFG_VIYA_HTTPROUTE_BACKEND_SERVICE: <viya_backend_service_name>
-# V4_CFG_VIYA_HTTPROUTE_BACKEND_PORT: 80
-
 ## Postgres
 # Optional for Google Cloud external postgres cloud-sql-proxy image version override
 # V4_CFG_POSTGRES_CLOUD_SQL_PROXY_VERSION: "1.38.0"
@@ -74,4 +66,4 @@ V4_CFG_CONNECT_ENABLE_LOADBALANCER: false
 ## 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"
+# V4_CFG_VIYA_STOP_SCHEDULE: "0 19 * * 1-5"