<p>I have 2 services and deployments deployed on minikube on local dev. Both are accessible when I run minikube start service. For the sake of simplicity I have attached code with only one service</p>
<p>However, ingress routing is not working</p>
<p>CoffeeApiDeployment</p>
<pre><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: coffeeapi-deployment
  labels:
    app: coffeeapi
spec:
  replicas: 1
  selector:
    matchLabels:
      app: coffeeapi
  template:
    metadata:
      labels:
        app: coffeeapi
    spec:
      containers:
      - name: coffeeapi
        image: manigupta31286/coffeeapi:latest
        env:
        - name: ASPNETCORE_URLS
          value: &quot;http://+&quot;
        - name: ASPNETCORE_ENVIRONMENT
          value: &quot;Development&quot;
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: coffeeapi-service
spec:
  selector:
    app: coffeeapi
  type: NodePort
  ports:
    - protocol: TCP
      port: 8080
      targetPort: 80
      nodePort: 30036
</code></pre>
<p>Ingress.yaml</p>
<pre><code>apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: myapp-ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
    - http:
        paths:
        - path: /coffee
          pathType: Prefix
          backend:
            service:
              name: coffeeapi-service
              port: 
                number: 8080
</code></pre>

user3522311
<p>You are missing the ingress class in the spec.</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: myapp-ingress
spec:
  ingressClassName: nginx # (or the class you configured)
</code></pre>
<p>Using <code>NodePort</code> on your service may also be problematic. At least it's not required since you want to use the ingress controller to route traffic via the <code>ClusterIP</code> and not use the <code>NodePort</code> directly.</p>
