This message was deleted.

The ingress rule matches host

<http://sub.domain.in|sub.domain.in>

- why would you expect it to match host

192.168.1.194

?

hi @creamy-pencil-82913, there is a reverse proxy setup which points sub.domain.in to these "192.168.1.194","192.168.1.209","192.168.1.239","192.168.1.249"

You still need to access it by the hostname for the rule to match. Are you doing so? Because that's not what you said you're doing.

hi @creamy-pencil-82913, thanks for the response. i have a static ip, which listens on multiple domains -- in this case subdomain.domain.in gets proxided to above ips. previously i was also able to reach the services with just the "192.168.1.194". this is my ingress

apiVersion: <http://networking.k8s.io/v1|networking.k8s.io/v1>
kind: Ingress
metadata:
  name: mfi-qa-ingress
  namespace: lms-qa
  annotations:
    <http://traefik.ingress.kubernetes.io/router.entrypoints|traefik.ingress.kubernetes.io/router.entrypoints>: websecure
    <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: traefik
    <http://traefik.ingress.kubernetes.io/router.middlewares|traefik.ingress.kubernetes.io/router.middlewares>: lms-qa-mfi-cors@kubernetescrd
spec:
  ingressClassName: traefik
  rules:
    - host: <http://subdomain.domain.in|subdomain.domain.in>
      http:
        paths:
          - backend:
              service:
                name: mfi-qa
                port:
                  number: 80
            path: /mfi
            pathType: Prefix
  tls:
  - hosts:
      - <http://subdomain.domain.in|subdomain.domain.in>
    secretName: <http://subdomain.domain.in|subdomain.domain.in>

many thanks again @creamy-pencil-82913.