You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/06/16 14:02:47 UTC

[GitHub] [camel-k] xytis opened a new issue #1535: No way to configure Ingress Trait with annotations

xytis opened a new issue #1535:
URL: https://github.com/apache/camel-k/issues/1535


   In many kubernetes deployments, machinery is in place that reacts to Ingress object annotations.
   
   What would be the prefered way to implement passing down these annotations to Ingress Trait object?
   
   Extra: Would it be possible to configure TLS on Ingress Trait object?


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [camel-k] nicolaferraro commented on issue #1535: No way to configure Ingress Trait with annotations

Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1535:
URL: https://github.com/apache/camel-k/issues/1535#issuecomment-644858419


   There's currently an easy way to pass labels as:
   
   ```
   kamel run ... --label mylabel=avalue -t owner.target-labels=mylabel
   ```
   
   The `--label` flag labels the integration, while the trait `owner.target-labels` allows to forward them to all sub resources (including the ingress).
   
   Although there's no corresponding `--annotation` flag (we should add it), if you manually annotate the integration with your annotations, there's a trait option `owner.target-annotations` to select the annotations to forward to sub resources.
   
   Btw, @xytis can you provide some more references about the way the ingress can be configured via annotations, so we may find a better way to configure it, including TLS support.


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [camel-k] xytis commented on issue #1535: No way to configure Ingress Trait with annotations

Posted by GitBox <gi...@apache.org>.
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:
users@infra.apache.org