xytis commented on issue #1535: URL: https://github.com/apache/camel-k/issues/1535#issuecomment-645188124
In my experience, Ingress objects generally require at least one annotation: `kubernetes.io/ingress.class: <ingress-class-name>`. Depending on ingress provider, there could be more annotations, that configure the provider. (Examples: [Traefik](https://docs.traefik.io/v1.7/configuration/backends/kubernetes/#annotations), [Nginx](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/), [AWS](https://kubernetes-sigs.github.io/aws-alb-ingress-controller/guide/ingress/annotation/)) Annotations can be complex JSON objects or multiline strings, so passing them through command line is not always viable. Regarding TLS support, it is a part of current standard [Ingress API](https://kubernetes.io/docs/concepts/services-networking/ingress/#tls), but I usually use it in conjunction with certificate manager, which requires even more [annotation based configuration](https://cert-manager.io/docs/usage/ingress/#supported-annotations). Overall, for now it seems that the best way to handle these kinds of scenarios would be to create the ingress object externally and use `service` trait to expose the integration. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
