👀 Views: 33 💬 Answers: 1 📅 Created: 2025-06-13

oci kubernetes ingress yaml

I'm following best practices but I'm learning this framework and I'm prototyping a solution and I'm experimenting with I've looked through the documentation and I'm still confused about After trying multiple solutions online, I still can't figure this out... I'm working with an scenario with my OCI Kubernetes cluster where I deployed multiple microservices using Helm charts, but I'm unable to access the services through the ingress controller. After deploying, I ran `kubectl get svc` and confirmed that the ingress service is up and running, but when I try to access the application URL, I get a 404 behavior. Here's the ingress resource I defined: ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: my-app-ingress annotations: nginx.ingress.kubernetes.io/rewrite-target: /$2 spec: rules: - host: myapp.example.com http: paths: - path: /app(/|$)(.*) pathType: Prefix backend: service: name: my-app-service port: number: 80 ``` I've also confirmed the DNS record for `myapp.example.com` points to the ingress's external IP. I tried checking the logs for the ingress controller with `kubectl logs -l app.kubernetes.io/name=ingress-nginx --tail=100`, but there's nothing indicating an behavior. I even made sure that the Helm chart is set up correctly to create the required services and routes. Is there something I'm missing, or could it be a misconfiguration in the ingress resource? Any help would be appreciated! My development environment is Ubuntu. Any ideas what could be causing this? Am I missing something obvious? For reference, this is a production application. I'm working in a Ubuntu 20.04 environment. Am I missing something obvious? I've been using Yaml for about a year now. I'd really appreciate any guidance on this. What am I doing wrong?