Merge pull request #422 from sassoftware/staging

6.4.0 - March 30, 2023
sassoftware · Mar 30, 2023 · f4795d7 · f4795d7
2 parents 7f86a79 + 5429014
commit f4795d7
Show file tree

Hide file tree

Showing 75 changed files with 551 additions and 39 deletions.
diff --git a/Dockerfile b/Dockerfile
@@ -14,7 +14,7 @@ RUN curl -sLO https://storage.googleapis.com/kubernetes-release/release/v{$kubec
 
 # Installation
 FROM baseline
-ARG helm_version=3.8.1
+ARG helm_version=3.9.4
 ARG aws_cli_version=2.7.22
 ARG gcp_cli_version=409.0.0
 

diff --git a/docker-entrypoint.sh b/docker-entrypoint.sh
@@ -1,4 +1,8 @@
 #!/usr/bin/env bash
+
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 set -e
 
 # setup container user

diff --git a/docs/CONFIG-VARS.md b/docs/CONFIG-VARS.md
@@ -37,7 +37,7 @@ Supported configuration variables are listed in the table below.  All variables
 
 | Name | Description | Type | Default | Required | Notes | Tasks |
 | :--- | ---: | ---: | ---: | ---: | ---: | ---: |
-| DEPLOY | Whether to deploy the SAS Viya platform or stop at generating kustomization.yaml and manifest | bool | true | false | | viya |
+| DEPLOY | Whether to deploy the SAS Viya platform and SAS Viya Platform Deployment Operator or stop at generating kustomization.yaml and manifests | bool | true | false | This flag can also prevent the uninstall of both the SAS Viya platform and SAS Viya Platform Deployment Operator | viya |
 | LOADBALANCER_SOURCE_RANGES | IP addresses to allow to reach the ingress | [string] | | true | When deploying in a cloud environment, be sure to add the cloud NAT IP address. | baseline, viya |
 | BASE_DIR | Path to store persistent files | string | $HOME | false | | all |
 | KUBECONFIG | Path to kubeconfig file | string | | true | | viya |
@@ -163,6 +163,11 @@ When V4_CFG_MANAGE_STORAGE is set to `true`, the `sas` and `pg-storage` storage
 | V4M_KEY | Path to TLS key to use for all monitoring/logging services | string | | false | As an alternative, you can set the per-service certificate. | cluster-logging, cluster-monitoring, viya-monitoring |
 | V4M_NODE_PLACEMENT_ENABLE | Whether to enable workload node placement for viya4-monitoring-kubernetes stack | bool | false | false | | cluster-logging, cluster-monitoring, viya-monitoring |
 | V4M_STORAGECLASS | StorageClass name | string | v4m | false | When V4_CFG_MANAGE_STORAGE is false, set to the name of your pre-existing StorageClass that supports ReadWriteOnce. | cluster-logging, cluster-monitoring, viya-monitoring |
+| V4M_ROUTING | Which routing type to use for viya4-monitoring-kubernetes applications | string | host-based | false | Supported values: [`host-based`, `path-based`] For host-based routing, the application name is part of the host name itself `https://dashboards.host.cluster.example.com/` For path-based routing, the host name is fixed and the application name is appended as a path on the URL `https://host.cluster.example.com/dashboards` | cluster-logging, cluster-monitoring |
+
+#### Open Source Kubernetes
+
+When deploying `cluster-logging` or `cluster-monitoring` applications to kubernetes cluster infrastructure provisioned with the [Open Source Kubernetes viya4-iac-k8s](https://github.com/sassoftware/viya4-iac-k8s) project, you must explicitly set the value for `V4M_STORAGECLASS` to a pre-existing Storage Class (for example: `local-storage`)  regardless of the value set for `V4_CFG_MANAGE_STORAGE`. While other storage classes can be used, the `local-storage` class is **recommended** for the Viya Monitoring and Loggging tools.
 
 ### Monitoring
 

diff --git a/docs/Troubleshooting.md b/docs/Troubleshooting.md
@@ -5,6 +5,9 @@
   - [SAS Viya Orchestration Tool](#sas-viya-orchestration-tool)
   - [SAS Viya Deployment Operator](#sas-viya-deployment-operator)
   - [EKS - Cluster Autoscaler Installation](#eks---cluster-autoscaler-installation)
+  - [kustomize - Generate deployment manifest](#kustomize---generate-deployment-manifest)
+  - [Ingress-Nginx issue - Unable to access SAS Viya Platform web apps](#ingress-nginx-issue---unable-to-access-sas-viya-platform-web-apps)
+
 
 ## Debug Mode
 Debug mode can be enabled by adding "-vvv" to the end of the docker or ansible commands
@@ -121,7 +124,7 @@ Note: As documented in our [CONFIG-VARS.md](./CONFIG-VARS.md), EKS 1.24 and lowe
 
 ### Solution:
 
-Note: If you used viya4-iac-aws:5.6.0 or never to create your infrastructure, these steps are not applicable for you. This role & policy should already be correct. 
+Note: If you used viya4-iac-aws:5.6.0 or newer to create your infrastructure, these steps are not applicable for you. This role & policy should already be correct. 
 
 1. Scale the `cluster-autoscaler-aws-cluster-autoscaler` deployment down to 0
       ```bash
@@ -143,4 +146,88 @@ Note: If you used viya4-iac-aws:5.6.0 or never to create your infrastructure, th
 2. Scale the `cluster-autoscaler-aws-cluster-autoscaler` deployment back to 1
       ```bash
       kubectl scale --replicas=1 deployment/cluster-autoscaler-aws-cluster-autoscaler
-      ```
+      ```
+
+
+## kustomize - Generate deployment manifest
+
+### Symptom:
+
+While deploying the SAS Viya platform to a cluster with the "viya" and "install" Ansible task tags specified, the following error message is encountered when the "vdm : kustomize - Generate deployment manifest" task executes:
+
+```bash
+TASK [vdm : kustomize - Generate deployment manifest] ************************
+fatal: [localhost]: FAILED! => changed=true
+  cmd:
+  - kustomize
+  - build
+  - <omitted>
+  - --load_restrictor=none
+  - -o
+  - <omitted>
+  delta: <omitted>
+  end: <omitted>
+  msg: non-zero return code
+  rc: 1
+  start: <omitted>
+  stderr: |-
+    Error: failed to apply json patch '- op: add
+      path: /spwc/volumeClaimTemplates/0/spec/storageClassName
+       value: sas': add operation does not apply: doc is missing path: "/spec/volumeClaimTemplates/0/spec/storageClassName": missing value
+  stderr_lines: <omitted>
+  stdout: ''
+  stdout_lines: <omitted>
+```
+
+### Diagnosis:
+
+The sas-data-agent-server-colocated component was added to the 2022.09 cadence of the SAS Viya Platform. That component contains a StatefulSet object which does not have a "/spec/volumeClaimTemplates/0/spec/storageClassName" path element.  For viya4-deployment releases prior to v5.4.0, a PatchTransformer expects to find that path element in each StatefulSet.
+
+### Solution:
+
+As of [release viya4-deployment:5.4.0](https://github.com/sassoftware/viya4-deployment/releases/tag/5.4.0), the StatefulSet PatchTransformer is intentionally skipped for the sas-data-agent-server-colocated component. Using [release viya4-deployment:5.4.0](https://github.com/sassoftware/viya4-deployment/releases/tag/5.4.0) or later for your SAS Viya Platform deployment will eliminate this error.
+
+
+## Ingress-Nginx issue - Unable to access SAS Viya Platform web apps
+### Symptom:
+After upgrading your AKS cluster's Kubernetes version to 1.24 or later, you are unable to access the SAS Viya Platform web apps. All the pods are running and errors are only seen in ingress-nginx logs:
+
+```bash
+W0320 20:15:25.141987       7 controller.go:1354] Using default certificate
+W0320 20:15:25.141997       7 controller.go:1347] Unexpected error validating SSL certificate "deploy/sas-ingress-certificate-5gc77h2dhg" for server "*.deploy.test.example.com": x509: certificate is valid for test-aks.example.com, not *.deploy.test.example.com
+W0320 20:15:25.142005       7 controller.go:1348] Validating certificate against DNS names. This will be deprecated in a future version
+W0320 20:15:25.142013       7 controller.go:1353] SSL certificate "deploy/sas-ingress-certificate-5gc77h2dhg" does not contain a Common Name or Subject Alternative Name for server "*.deploy.test.example.com": x509: certificate is valid for test-aks.example.com, not *.deploy.test.example.com
+```
+
+### Diagnosis:
+This issue is related to Azure LoadBalancer’s probing. The appProtocol support inside cloud provider has broken ingress-nginx for AKS clusters >=1.22. The issue was caused by two reasons:
+* the new version of nginx ingress controller added appProtocol and its probe path has to be `/healthz`;
+* the new version of cloud-controller-manager added HTTP probing with default path `/` for appProtocol=http services.
+
+The `Custom Load Balancer health probe` section in the [Azure LoadBalancer](https://cloud-provider-azure.sigs.k8s.io/topics/loadbalancer/#custom-load-balancer-health-probe) document states that:
+
+>Tcp, Http and Https are three protocols supported by load balancer service. Currently, the default protocol of the health probe varies among services with different transport protocols, app protocols, annotations and external traffic policies.
+>1. for local services, HTTP and /healthz would be used. The health probe will query NodeHealthPort rather than actual backend service
+>2. for cluster TCP services, TCP would be used.
+>3. for cluster UDP services, no health probes.
+>
+> Since v1.20, service annotation `service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path` is introduced to determine the health probe behavior.
+  >- For clusters <=1.23, spec.ports.appProtocol would only be used as probe protocol when `service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path` is also set.
+  > - For clusters >1.24, spec.ports.appProtocol would be used as probe protocol and `/` would be used as default probe request path (`service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path` could be used to change to a different request path).
+
+To resolve this issue the ingress-nginx version should be 1.3.0 (or later) with the following annotation configured :
+> --set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path"=/healthz
+
+### Solution:
+For Users upgrading their AKS cluster's Kubernetes version to 1.24 (or later) and used viya4-deployment v6.3.0 (or prior) for the SAS Viya Platform deployment, you must use viya4-deployment v6.4.0 (or later) and re-run the baseline install task.
+
+If you prefer to continue using the existing viya4-deployment version then add the following in your ansible-var.yaml and re-run baseline install task :
+
+```bash
+INGRESS_NGINX_CHART_VERSION: 4.3.0
+INGRESS_NGINX_CONFIG:
+  controller:
+    service:
+      annotations:
+        service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path: /healthz
+```
diff --git a/docs/user/AnsibleUsage.md b/docs/user/AnsibleUsage.md
@@ -109,3 +109,11 @@ Any number of tasks can be run at the same time. An action can run against a sin
     -e JUMP_SVR_PRIVATE_KEY=$HOME/.ssh/id_rsa \
     playbooks/playbook.yaml --tags "baseline,viya,cluster-logging,cluster-monitoring,viya-monitoring,uninstall"
   ```
+
+### Ansible Config
+
+In the examples above, we are running `ansible-playbook` from within the project directory. This means Ansible will automatically load the project's `ansible.cfg` file which contains configuration settings to properly run this project's playbook. If you are calling the playbook from a directory outside of this project's folder, it is important to set the following Ansible environment variable prior to running the playbook so that the configuration file gets loaded.
+
+```bash
+export ANSIBLE_CONFIG=${WORKSPACE}/viya4-deployment/ansible.cfg
+```
diff --git a/docs/user/SingleStore.md b/docs/user/SingleStore.md
@@ -8,9 +8,27 @@ If your SAS software order included SAS Viya with SingleStore, additional requir
 
 ## Deploying SAS Viya with SingleStore Using SAS Viya 4 Deployment
 
-You can deploy SAS Viya with SingleStore into a Kubernetes cluster that is running in Microsoft Azure. The [SAS Viya 4 Infrastructure as Code (IaC) for Microsoft Azure](https://github.com/sassoftware/viya4-iac-azure) GitHub project can automatically provision the required infrastructure components that support SAS Viya with SingleStore deployments. 
+You can deploy SAS Viya with SingleStore into a Kubernetes cluster running under:
+- Azure Kubernetes Service (AKS) in Microsoft Azure
+- Elastic Kubernetes Service (EKS) in Amazon Web Services (AWS)
+- Open Source Kubernetes on your own machines
 
-Refer to the [SingleStore sample input file](https://github.com/sassoftware/viya4-iac-azure/blob/main/examples/sample-input-singlestore.tfvars) for Terraform configuration values that create an Azure cluster suitable for deploying SAS Viya and SingleStore.
+## Cluster Provisioning for SAS Viya with SingleStore
+
+### Azure Kubernetes Service (AKS) Cluster in Microsoft Azure
+
+The [SAS Viya 4 IaC for Microsoft Azure](https://github.com/sassoftware/viya4-iac-azure) GitHub project can automatically provision the required infrastructure components that support SAS Viya with SingleStore deployments. 
+Refer to the [SingleStore sample input file](https://github.com/sassoftware/viya4-iac-azure/blob/main/examples/sample-input-singlestore.tfvars) for Terraform configuration values that create an AKS cluster that is suitable for deploying SAS Viya and SingleStore.
+
+### EKS Cluster in AWS
+
+The [SAS Viya 4 IaC for AWS](https://github.com/sassoftware/viya4-iac-aws) GitHub project can automatically provision the required infrastructure components that support SAS Viya with SingleStore deployments. 
+Refer to the [SingleStore sample input file](https://github.com/sassoftware/viya4-iac-aws/blob/main/examples/sample-input-singlestore.tfvars) for Terraform configuration values that create an EKS cluster that is suitable for deploying SAS Viya and SingleStore.
+
+### Open Source Kubernetes Cluster
+
+The [SAS Viya 4 Infrastructure as Code (IaC) for Open Source Kubernetes](https://github.com/sassoftware/viya4-iac-k8s) GitHub project can automatically provision the required infrastructure components that support SAS Viya with SingleStore deployments. 
+Refer to the [SingleStore sample input file](https://github.com/sassoftware/viya4-iac-k8s/blob/main/examples/vsphere/sample-terraform-static-singlestore.tfvars) for Terraform configuration values that create an Open Source Kubernetes cluster that is suitable for deploying SAS Viya and SingleStore.
 
 ## Customizing SingleStore Deployment Overlays
 

diff --git a/playbooks/playbook.yaml b/playbooks/playbook.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 - hosts: localhost
   tasks:
     - name: global tmp dir

diff --git a/roles/baseline/defaults/main.yml b/roles/baseline/defaults/main.yml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 V4_CFG_TLS_MODE: "full-stack" # other valid values are front-door, ingress-only, and disabled
 V4_CFG_RWX_FILESTORE_PATH: /export
 V4_CFG_INGRESS_TYPE: ingress
@@ -63,6 +66,13 @@ INGRESS_NGINX_CONFIG:
           command: ["/bin/sh", "-c", "sleep 5; /usr/local/nginx/sbin/nginx -c /etc/nginx/nginx.conf -s quit; while pgrep -x nginx; do sleep 1; done"]
     terminationGracePeriodSeconds: 600
 
+# Add annotation to include Azure load-balancer health probe request path
+INGRESS_NGINX_AZURE_LB_HEALTH_PROBE_CONFIG:
+  controller:
+    service:
+      annotations:
+        service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path: /healthz
+
 # Update default load-balancer for AWS to be NLB
 INGRESS_NGINX_AWS_NLB_CONFIG:
   controller:

diff --git a/roles/baseline/tasks/cert-manager.yaml b/roles/baseline/tasks/cert-manager.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - name: Deploy cert-manager
   kubernetes.core.helm:

diff --git a/roles/baseline/tasks/cluster-autoscaler.yaml b/roles/baseline/tasks/cluster-autoscaler.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 
 - name: Set the default CLUSTER_AUTOSCALER_CHART_VERSION if not specified

diff --git a/roles/baseline/tasks/contour.yaml b/roles/baseline/tasks/contour.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - name: Deploy contour
   kubernetes.core.helm:

diff --git a/roles/baseline/tasks/ebs-csi-driver.yaml b/roles/baseline/tasks/ebs-csi-driver.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - name: Deploy ebs-csi-driver
   kubernetes.core.helm:

diff --git a/roles/baseline/tasks/ingress-nginx.yaml b/roles/baseline/tasks/ingress-nginx.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - set_fact:
     INGRESS_NGINX_CONFIG: "{{ INGRESS_NGINX_CONFIG |combine(private_ingress[PROVIDER], recursive=True)}}"
@@ -37,6 +40,15 @@
     - install
     - update
 
+- name: Update INGRESS_NGINX_CONFIG to add Azure load-balancer health probe request path
+  set_fact:
+    INGRESS_NGINX_CONFIG: "{{ INGRESS_NGINX_CONFIG|combine(INGRESS_NGINX_AZURE_LB_HEALTH_PROBE_CONFIG, recursive=True)}}"
+  when:
+    - PROVIDER == "azure"
+  tags:
+    - install
+    - update    
+
 - name: Apply Mitigation for CVE-2021-25742
   block:
     - name: Retreive K8s cluster information

diff --git a/roles/baseline/tasks/main.yaml b/roles/baseline/tasks/main.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 
 ---
 - name: Include nfs-subdir-external-provisioner

diff --git a/roles/baseline/tasks/metrics-server.yaml b/roles/baseline/tasks/metrics-server.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - name: Check for metrics service
   kubernetes.core.k8s_info:

diff --git a/roles/baseline/tasks/nfs-subdir-external-provisioner.yaml b/roles/baseline/tasks/nfs-subdir-external-provisioner.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - name: Remove deprecated nfs-client-provisioner
   kubernetes.core.helm:

diff --git a/roles/common/defaults/main.yml b/roles/common/defaults/main.yml
@@ -1,2 +1,5 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 V4_CFG_POSTGRES_SERVERS: 
   default: {}
diff --git a/roles/common/lookup_plugins/tfstate.py b/roles/common/lookup_plugins/tfstate.py
@@ -1,3 +1,7 @@
+#
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+#
 from __future__ import (absolute_import, division, print_function)
 __metaclass__ = type
 

diff --git a/roles/common/tasks/main.yaml b/roles/common/tasks/main.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 - name: Load config file
   include_vars:
     file: "{{ CONFIG }}"

diff --git a/roles/common/tasks/migrations.yaml b/roles/common/tasks/migrations.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 
 
 - block:

diff --git a/roles/common/tasks/task-validations.yaml b/roles/common/tasks/task-validations.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 
 - name: task validation

diff --git a/roles/istio/defaults/main.yml b/roles/istio/defaults/main.yml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 target_arch: x86_64
 loadBalancerSourceRanges: ["109.232.56.224/27", "149.173.0.0/16", "194.206.69.176/28"]

diff --git a/roles/istio/tasks/main.yml b/roles/istio/tasks/main.yml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - name: Download istio
   shell: 

diff --git a/roles/istio/tests/test.yml b/roles/istio/tests/test.yml
@@ -1,5 +1,8 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - hosts: localhost
   remote_user: root
   roles:
-    - deploy
+    - deploy
diff --git a/roles/istio/vars/main.yml b/roles/istio/vars/main.yml
@@ -1,2 +1,5 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
-# vars file for deploy
+# vars file for deploy
diff --git a/roles/jump-server/defaults/main.yml b/roles/jump-server/defaults/main.yml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 JUMP_SVR_RWX_FILESTORE_PATH: /viya-share
 folder_owner: nobody
-folder_group: nobody
+folder_group: nobody
diff --git a/roles/jump-server/tasks/main.yml b/roles/jump-server/tasks/main.yml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 ---
 - name: jump-server - add host
   add_host:

diff --git a/roles/monitoring/defaults/main.yaml b/roles/monitoring/defaults/main.yaml
@@ -1,3 +1,6 @@
+# Copyright © 2020-2023, SAS Institute Inc., Cary, NC, USA. All Rights Reserved.
+# SPDX-License-Identifier: Apache-2.0
+
 KUBECONFIG: ~/.kube/config
 NAMESPACE: null
 V4_CFG_MANAGE_STORAGE: true
@@ -9,6 +12,7 @@ V4M_NODE_PLACEMENT_ENABLE: false
 V4M_BASE_DOMAIN: "{{ V4_CFG_BASE_DOMAIN }}"
 V4M_CERT: null
 V4M_KEY: null
+V4M_ROUTING: host-based
 
 V4M_LOGGING_NAMESPACE: logging
 V4M_MONITORING_NAMESPACE: monitoring