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

Claus Ibsen commented on CAMEL-22144:
-------------------------------------

okay so fixed for spring-boot, that now uses 9876

for quarkus it seems that jkube does not understand quarkus.management.port

> camel-jbang: Kubernetes plugin management port for liveness/readiness
> ---------------------------------------------------------------------
>
>                 Key: CAMEL-22144
>                 URL: https://issues.apache.org/jira/browse/CAMEL-22144
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jbang
>    Affects Versions: 4.12.0
>            Reporter: Gaelle Fournier
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 4.14.0
>
>
> The generated project still uses 8080 as port for the liveness and readiness 
> port in the manifest when it is supposed to be 9876 with the runtime 
> spring-boot.
>  
>  
> {code:java}
>   kind: Deployment
>   metadata:
>     labels:
>       camel.apache.org/app: camel-quarkus
>       app.kubernetes.io/runtime: camel
>       camel/integration-runtime: camel
>       app.kubernetes.io/name: camel-quarkus
>       app.openshift.io/runtime: camel
>       app: camel-quarkus
>       provider: jkube
>       version: 1.0-SNAPSHOT
>       group: org.example.project
>       app.kubernetes.io/part-of: org.example.project
>       app.kubernetes.io/managed-by: jkube
>       app.kubernetes.io/version: 1.0-SNAPSHOT
>     name: camel-quarkus
>   spec:
>     replicas: 1
>     revisionHistoryLimit: 2
>     selector:
>       matchLabels:
>         app.kubernetes.io/name: camel-quarkus
>         app: camel-quarkus
>         provider: jkube
>         group: org.example.project
>         app.kubernetes.io/part-of: org.example.project
>         app.kubernetes.io/managed-by: jkube
>     template:
>       metadata:
>         labels:
>           app.kubernetes.io/name: camel-quarkus
>           app: camel-quarkus
>           provider: jkube
>           version: 1.0-SNAPSHOT
>           group: org.example.project
>           app.kubernetes.io/part-of: org.example.project
>           app.kubernetes.io/managed-by: jkube
>           app.kubernetes.io/version: 1.0-SNAPSHOT
>         name: camel-quarkus
>       spec:
>         containers:
>         - env:
>           - name: KUBERNETES_NAMESPACE
>             valueFrom:
>               fieldRef:
>                 fieldPath: metadata.namespace
>           image: camel-quarkus:1.0-SNAPSHOT
>           imagePullPolicy: IfNotPresent
>           livenessProbe:
>             failureThreshold: 3
>             httpGet:
>               path: /observe/health/live
>               port: 8080
>               scheme: HTTP
>             initialDelaySeconds: 10
>             successThreshold: 1
>           name: camel-quarkus
>           ports:
>           - containerPort: 8080
>             name: http
>             protocol: TCP
>           readinessProbe:
>             failureThreshold: 3
>             httpGet:
>               path: /observe/health/ready
>               port: 8080
>               scheme: HTTP
>             initialDelaySeconds: 5
>             successThreshold: 1
>           securityContext:
>             privileged: false
>           startupProbe:
>             failureThreshold: 3
>             httpGet:
>               path: /observe/health/started
>               port: 8080
>               scheme: HTTP
>             initialDelaySeconds: 5
>             successThreshold: 1{code}
>  
>  
>  
> At least adding 
> {noformat}
> management.server.port=9876{noformat}
>  and the port in the container should help at list for spring-boot 
> {code:java}
> containerPort: 9876
> name: management
> protocol: TCP{code}
> I did not try quarkus and camel-main but there should be a similar issue. 



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

Reply via email to