cfitzw commented on issue #5981: URL: https://github.com/apache/camel-k/issues/5981#issuecomment-2541579029
**TL;DR** - I think this is bubbling up into a bigger issue. @squakez I have a working build, allowing a string array on the ingress.path, however, I have some doubts... 1. This would become a breaking change == any integration having an `ingress.path=<string>` set would break. _Possibly some code could be implemented to auto-convert string into array... but maybe not worth the effort based on below._ 2. This isn't fully solving the problem... IMO, the IngressTrait should follow the APIs hierarchy, starting from here: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#ingressspec-v1-networking-k8s-io _This would allow any number of IngressRules (which has it's own sub-structure), meaning, you could specify multiple hosts, and for those hosts, multiple paths, which may also have their own associated pathType._ Best visual example of the hierarchy (from https://v1-30.docs.kubernetes.io/docs/concepts/services-networking/ingress/#hostname-wildcards): ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress-wildcard-host spec: rules: - host: "foo.bar.com" http: paths: - pathType: Prefix path: "/bar" backend: service: name: service1 port: number: 80 - host: "*.foo.com" http: paths: - pathType: Prefix path: "/foo" backend: service: name: service2 port: number: 80 ``` Please let me know your thoughts. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
