AGIC is creating a backend pool in App GW with pod IP instead of AKS service IP

[venkateshbabud]

AGIC is creating backend pools in the Application Gateway with the Pod IPs as targets. How can we configure it to expose the LoadBalancer service IP instead of the Pod IP?

I'm using the below ingress yml file to create Ingress resource:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: dev-ingress
namespace: default
annotations:
appgw.ingress.kubernetes.io/ssl-redirect: "true"
appgw.ingress.kubernetes.io/use-private-ip: "true"
#appgw.ingress.kubernetes.io/backend-protocol: "http"
#appgw.ingress.kubernetes.io/use-istio-mtls: "false"
appgw.ingress.kubernetes.io/use-istio-pool: "true"
#appgw.ingress.kubernetes.io/use-service-principal: "false"
#appgw.ingress.kubernetes.io/use-external-service: "true"
#appgw.ingress.k8s.io/backend-address-type: "External"
appgw.ingress.kubernetes.io/backend-hostname: "10...**"
appgw.ingress.kubernetes.io/health-probe-status-codes: "200-599"
spec:
ingressClassName: azure-application-gateway
tls:
- secretName: agic-tls-secret
rules:
- host:
http:
paths:
- path: /v1/user-service/*
pathType: Prefix
backend:
service:
name: sv-default-service
port:
number: 80

[teks666]

@venkateshbabud did you resolve this? Are you using a non-AKS K8S cluster?