👀 Views: 115 💬 Answers: 1 📅 Created: 2025-06-16

kubernetes traefik ingress yaml

After trying multiple solutions online, I still can't figure this out. I'm experiencing issues with routing HTTP traffic through Traefik Ingress in my Kubernetes cluster running on Minikube. I have a simple setup with two services: a frontend and a backend, but Traefik doesn't seem to route traffic to the frontend service as expected. Here’s my minimal configuration for the Ingress resource: ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: my-ingress annotations: traefik.ingress.kubernetes.io/router.entrypoints: web spec: rules: - host: my-app.local http: paths: - path: / pathType: Prefix backend: service: name: frontend-service port: number: 80 ``` I’ve also deployed my frontend and backend services like this: ```yaml apiVersion: v1 kind: Service metadata: name: frontend-service spec: type: ClusterIP ports: - port: 80 targetPort: 80 selector: app: frontend --- apiVersion: v1 kind: Service metadata: name: backend-service spec: type: ClusterIP ports: - port: 8080 targetPort: 8080 selector: app: backend ``` To access my application, I'm editing the /etc/hosts file to point `my-app.local` to the Minikube IP. However, when I try to access `http://my-app.local`, I get a `404 Not Found` behavior from Traefik. I've confirmed that Traefik is running and I can access the Traefik dashboard, but it doesn’t show any routes for my Ingress. I've also checked the logs for Traefik and see entries like: ``` behavior: no service "frontend-service" found ```. I've verified that the service is indeed created and is in the same namespace as the Ingress. I’ve tried redeploying Traefik and the Ingress resource multiple times without success. Is there something I'm missing in my configuration? Any insights on how to troubleshoot this would be greatly appreciated! Is there a simpler solution I'm overlooking? Could this be a known issue?