Issue with BrownField Deployment (backendPool, HttpSetting and HealthProbe)

[nreddipalle]

Describe the bug Existing AppGateway configuration is not correct after AGIC setup is completed.

This is the Ingress setup.. `apiVersion: extensions/v1beta1 kind: Ingress metadata: name: tasks-dev-ingress namespace: tasks-dev annotations: kubernetes.io/ingress.class: azure/application-gateway
appgw.ingress.kubernetes.io/cookie-based-affinity: "true"

spec: tls:

• hosts:
  • senseimsvctasksweu-dev.senseilabs.com secretName: sensei-ingress-tls rules:
• host: senseimsvctasksweu-dev.senseilabs.com http: paths:
  • backend: serviceName: web-ui servicePort: 80 path: /tasks/ ` App Gateway Rule Setup (Pointing to default backendpool and defaultHttpSetting even AGIC created a new backend pool and new httpsetting)

Let me know if any additional info is required. Thanks.

[akshaysngupta]

@nreddipalle You have to specify a ingress rule for path /. That is used to set the default backend pool and default backend http settting in Path-based rule.

Try modify your existing ingress yaml by changing /tasks/ -> /

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: tasks-dev-ingress
  namespace: tasks-dev
annotations:
  kubernetes.io/ingress.class: azure/application-gateway
  appgw.ingress.kubernetes.io/cookie-based-affinity: "true"
spec:
  tls:
    - hosts:
      - senseimsvctasksweu-dev.senseilabs.com
      secretName: sensei-ingress-tls
  rules:
  - host: senseimsvctasksweu-dev.senseilabs.com
    http:
    paths:
      path: /
      backend:
        serviceName: web-ui
        servicePort: 80

[horocrux]

Hi @akshaysngupta, I had the same issue and I solved it by doing your recomendation, but why is needed the "/" route?, What if I need to use always a path to point to my services, should I put a dummy service with "/" route?, Whats is your recommendation in that escenario?

@nreddipalle You have to specify a ingress rule for path /. That is used to set the default backend pool and default backend http settting in Path-based rule.

Try modify your existing ingress yaml by changing /tasks/ -> /

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: tasks-dev-ingress
  namespace: tasks-dev
annotations:
  kubernetes.io/ingress.class: azure/application-gateway
  appgw.ingress.kubernetes.io/cookie-based-affinity: "true"
spec:
  tls:
    - hosts:
      - senseimsvctasksweu-dev.senseilabs.com
      secretName: sensei-ingress-tls
  rules:
  - host: senseimsvctasksweu-dev.senseilabs.com
    http:
    paths:
      path: /
      backend:
        serviceName: web-ui
        servicePort: 80