Ingress controller fails to post config on IPv6 cluster

Questions
1

Hi,

I installed Kong 3.2 version using latest helm chart(2.19.0) successfully. But my application’s health endpoint is not accessible via kong.

Ingress-controller logs
level=error msg=“entity tags missing fields” error=“no name” name=
level=error msg=“could not update kong admin” error=“performing update for https://localhost:8444 failed: failed posting new config to /config: got status code 400” subsystem=dataplane-synchronizer

Proxy logs
127.0.0.1 - - “POST /config?check_hash=1&flatten_errors=1 HTTP/1.1” 400 400 “-” “Go-http-client/1.1”

Pod status
ICORE-VER-223066194-820:~/app # kubectl get po
NAME READY STATUS RESTARTS AGE
apigateway-kong-5b467bb994-p4ts4 2/2 Running 0 8m45s
python-ui-5469468c5-679gf 1/1 Running 0 6m19s

Ingress Object:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
kubernetes.io/ingress.class: nginx
service.alpha.kubernetes.io/ipv6: “true”
creationTimestamp: “2023-04-20T04:47:06Z”
generation: 1
name: python-ingress
namespace: default
resourceVersion: “122095”
uid: abb8eb2b-7caa-474f-a0a1-f9c6326ad145
spec:
rules:

  • http:
    paths:
    • backend:
      service:
      name: python-ui-service
      port:
      number: 6000
      path: /health
      pathType: Exact
      status:
      loadBalancer:
      ingress:
    • ip: 2001:db8:42:1::3ca1

Below is the output of curl command:
curl http://[ipv6Address]:31221/health
{“message”:“no Route matched with those values”}

I am not able to find the issue here. Kindly help

Versions:
Kubernetes = 1.23.7
Helm Chart = 2.19.0
Kong = 3.2
Ingress Controller = 2.9