right - i’ve got gitlab serving the login page via an azure application gateway ingress controller. the answer was to create a ingress config in kubectl and point it at gitlab-webservice-default on port 8080. now however, i am faced with another problem; any attempt to log in, on any browser, from any machine, gets a 422 " The change you requested was rejected" response. i have not yet set up SSL, so it is http throughout, and i disabled certs with these settings in the helm install command:
1. Remove ingress controller
–set nginx-ingress.enabled=false
2. Disable tls
–set certmanager.install=false
–set global.ingress.configureCertmanager=false
There are several specific items one must perform in order to accomplish this. I am very close to having this same type of arrangement deployed to an azure application gateway as well. I have successfully deployed this to a class of azure\application-gateway but am finding a few small problems myself. Could you provide your YAML that you used to deploy it to the application gateway? How did you create your trusted root cert? Are you using end to end TLS and uploading the trusted root cert and SSL cert to the application gateway? I have followed the page you reference as well, but I found this example to be a little easier to follow: Tutorial: Setting up E2E SSL - Application Gateway Ingress Controller