Hi All,
I'm currently in the process of deploying SAS Viya on a new AKS cluster that utilizes the Azure Application Gateway Ingress Controller
, and I was wondering if anyone has experience using this combination and whether SAS Viya is compatible with it.
I would like to first run the pre-installation check provided in this repository: https://github.com/sassoftware/viya4-ark/tree/main/pre_install_report however the available ingress options mentioned there are limited tonginx
or openshift
, and as far as I'm aware, the Azure Application Gateway Ingress Controller
is not based onnginx
.
Would I need to deploy a separate nginx ingress controller
or is there a way to make the Azure Application Gateway Ingress Controller
work with SAS Viya?
Thank you in advance.
Apologies if I might have misunderstood your response, but in my current setup, which I, unfortunately, am unable to alter, the Azure Application Gateway Ingress Controller
has already been deployed, and it's been done via Helm.
My confusion though, is that although SAS Viya on AKS appears to support the standard NGINX Ingress Controller
, I don't know if it supports the Azure Application Gateway Ingress Controller
, which I believe is a distinct solution with different functionalities and implementations when compared to the NGINX Ingress Controller
and I'm trying to figure out if I am able to use this with my SAS Viya deployment, or if I would need to deploy a separate NGINX Ingress Controller
Hi,
I need to configure something similar. Were you able to setup this successfully? Is so, can you please explain how did you enable the use of Application Gateway?
I had installed NGINX with Load Balancer and Private IP and was able to access SAS Viya within the cluster network ... but I am not sure how to use the Application Gateway to enable access externally.
Thank you!
We had similar situation where we required two types of Interfaces - 1. External 2. Internal.
In our case we used F5 Load balancer (Layer 7) for External traffic and Ngnix (and Azure Internal Loadbalancer) for Internal traffic. Both F5 and Ngnix were configured to Listen on Port 443.
In F5 backend Pool configuration we added an Internal IP Address of Ngnix and in NSG we allowed F5 IP Address.
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!