You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2025/01/08 14:43:00 UTC

[jira] [Commented] (CAMEL-21405) camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress traits

    [ https://issues.apache.org/jira/browse/CAMEL-21405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911116#comment-17911116 ] 

Claus Ibsen commented on CAMEL-21405:
-------------------------------------

Is this still relevant, or do we try to generate all the runtimes in the same way with jkube and if so, then this is maybe not needed anymore ?

> camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress traits
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-21405
>                 URL: https://issues.apache.org/jira/browse/CAMEL-21405
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>    Affects Versions: 4.x
>            Reporter: Gaelle Fournier
>            Priority: Minor
>
> In Kubernetes plugin, Ingress trait (service exposure) is only available through the generated kubernetes manifest.
> To leverage quarkus cloud readyness we should add for quarkus runtime cases the use of : [https://quarkus.io/guides/deploying-to-kubernetes#exposing-your-application-in-kubernetes] 
> There is a bug on quarkus kubernetes extension that needs to be fixed before this can be done for non "Prefix" type-path route to work : https://github.com/quarkusio/quarkus/issues/43783



--
This message was sent by Atlassian Jira
(v8.20.10#820010)