nginx path base routing it not working / is not responding - kubernetes-ingress

Question

I have nginx deployed with helm
[rke#k8gui apps]$ kubectl get all -n ingress-nginx
NAME READY STATUS RESTARTS AGE
pod/ingress-nginx-controller-fcrj2 1/1 Running 0 113m
pod/ingress-nginx-controller-jkpsm 1/1 Running 0 113m
pod/ingress-nginx-controller-v2dfh 1/1 Running 0 113m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/ingress-nginx-controller LoadBalancer 10.43.132.34 192.168.33.100 80:30345/TCP,443:31347/TCP 113m
service/ingress-nginx-controller-admission ClusterIP 10.43.84.182 <none> 443/TCP 113m
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/ingress-nginx-controller 3 3 3 3 3 kubernetes.io/os=linux 113m
The external IP is received via metallb.
I am trying to test path base nginx routing but not working
apple.yaml
kind: Pod
apiVersion: v1
metadata:
name: apple-app
labels:
app: apple
spec:
containers:
- name: apple-app
image: hashicorp/http-echo
args:
- "-text=apple"
---
kind: Service
apiVersion: v1
metadata:
name: apple-service
spec:
selector:
app: apple
ports:
- port: 5678 # Default port for image
banana.yaml
kind: Pod
apiVersion: v1
metadata:
name: banana-app
labels:
app: banana
spec:
containers:
- name: banana-app
image: hashicorp/http-echo
args:
- "-text=banana"
---
kind: Service
apiVersion: v1
metadata:
name: banana-service
spec:
selector:
app: banana
ports:
- port: 5678 # Default port for image
ing.yaml
[rke#k8gui apps]$ more ing.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: example-ingress
annotations:
ingress.kubernetes.io/rewrite-target: /
spec:
ingressClassName: nginx
rules:
- http:
paths:
- path: /apple
pathType: Prefix
backend:
service:
name: apple-service
port:
number: 5678
- path: /banana
pathType: Prefix
backend:
service:
name: banana-service
port:
number: 5678
[rke#k8gui apps]$ kubectl get ingress
NAME CLASS HOSTS ADDRESS PORTS AGE
example-ingress nginx * 192.168.33.100 80 12m
but curling 192.168.33.100/apple or 192.168.33.100/banana is not working
any idea?
curling to the pod IP is working fine any idea what is missing?