Closed tclehman closed 9 months ago
Bumping this thread
@thpang Would you be able to comment on this? We are trying to get an application gateway to work with this deployment, but really having some difficulty getting it to work.
Hello,
Here is the latest update on this issue:
We can validate connectivity between the ingress controller and the cluster. We are also able to validate connectivity from the app gateway to the ingress controller. The URL is still not properly resolving. The issue appears to be that the automation that is run through the GitHub page shown here https://github.com/sassoftware/viya4-deployment is still pointing the ingress service to the load balancer IP address.
We need clarification on how to change the nginx-ingress-controller service to point to the newly created application gateway IP address, rather than the Load Balancer IP address that is getting created from the automation by default.
@tclehman, Are you still having the issue?
Closing this issue due to inactivity. Please feel free to open the issue if the issue persists.
The current setup using default inputs will create a public load balancer as the front-end of the application. I see on this page page that it mentions that "You can also deploy a load balancer or application gateway to mediate data flows between SAS Viya components and the ingress controller."
I do not see documentation on how to use an application gateway rather than a load balancer. Is there documentation on this and if-so can you point me to it or instruct me as to how to deploy using one rather than a load balancer?