ingress not working after deployment jkube maven

[semanticfire]

Due to a downstream update, a project using jkube was deployed by our CI system.

When trying to load the application from the web address, I get a 404 from nginx signaling some wiring is wrong.

If I delete the Ingres from the console, and create it based on the contents of, target/classes/META-INF/jkube/kubernetes/project-ingress.yml it starts working immediately.

src/main/jkube/ingress.yml

apiVersion: networking.k8s.io/v1
metadata:
  name: ${k8sgroupId}-${project.artifactId}-ingress
  annotations:
    ingress.kubernetes.io/rewrite-target: /
    cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
  tls:
  - hosts:
    - ${proj.hostname}
    secretName: letsencrypt-${k8sgroupId}-${project.artifactId}
  rules:
  - host: ${proj.hostname}
    http:
      paths:
        - path: /
          pathType: Prefix
          backend:
            service:
              name: ${k8sgroupId}-${project.artifactId}-service
              port: 
                number: ${tomee.port}

Client Version: v1.25.4
Server Version: v1.21.13-3+cbc10c94808907

Original jkube version was 1.4.0 tried with 1.10.1 but no changes, any hints are greatly appreciated!

[rohanKanojia]

Have you tried checking diff against working Ingress YAML and the one generated by jkube?

[semanticfire]

I use k8s:apply

[rohanKanojia]

I tried reproducing your issue by placing ingress.yml in src/main/jkube in a demo project but I was able to access the application via Ingress.

Could you please check if there is any significant difference between the generated Ingress (target/classes/META-INF/jkube/kubernetes/project-ingress.yml) and one that gets applied after k8s:apply (kubectl get ing $name -o yaml)

[semanticfire]

So the difference between the jkube uploaded and console created result it:

spec:
  ingressClassName: public

[semanticfire]

Which seems to do the trick once added to my yml in the src\main\jkube\ingress.yml

So, problem, solved, what is the explanation?

[rohanKanojia]

Umm, I'm not sure. Documentation for .spec.ingressClassName says it maps to current IngressClass resource.

jkube-ingress-fragment : $ kubectl get ingressclass
NAME    CONTROLLER             PARAMETERS   AGE
nginx   k8s.io/ingress-nginx   <none>       71m

When I set ingressClassName: public in src/main/jkube.ingress.yml I start getting 404 Not Found error. If I set it to ingressClassName: nginx it works 😕

[semanticfire]

Adding

spec:
  ingressClassName: public

Solved the problem