[
https://issues.apache.org/jira/browse/CAMEL-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17936871#comment-17936871
]
Claudio Miranda commented on CAMEL-21835:
-----------------------------------------
The solution was to skip the k8s:resource task and run k8s:apply and set
{{-Djkube.kubernetesManifest=src/main/jkube/service.yml}}.
> camel-jbang-kubernetes run fails when using knative traits
> -----------------------------------------------------------
>
> Key: CAMEL-21835
> URL: https://issues.apache.org/jira/browse/CAMEL-21835
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Affects Versions: 4.10.1
> Reporter: Claudio Miranda
> Assignee: Claudio Miranda
> Priority: Minor
>
> When use the --trait knative-service.enabled=true it correctly generates the
> src/main/jkube/service.yaml with the knative service.
> however when building the maven project, the k8s:resource and k8s:deploy
> tasks generates the non knative Deployment in
> target/classes/META-INF/jkube/kubernetes/http-log-deployment.yml
> {code}
> INFO] --- k8s:1.18.1:resource (default) @ http-log ---
> [INFO] k8s: Using resource templates from
> /home/claudio/alphaworks/projects/camel/.camel-jbang-run/http-log/src/main/jkube
> [INFO] k8s: jkube-controller: Adding a default Deployment
> [INFO] k8s: jkube-healthcheck-quarkus: Adding readiness probe on port 8080,
> path='/q/health/ready', scheme='HTTP', with initial delay 5 seconds
> [INFO] k8s: jkube-healthcheck-quarkus: Adding liveness probe on port 8080,
> path='/q/health/live', scheme='HTTP', with initial delay 10 seconds
> [INFO] k8s: jkube-healthcheck-quarkus: Adding startup probe on port 8080,
> path='/q/health/started', scheme='HTTP', with initial delay 5 seconds
> [INFO] k8s: jkube-revision-history: Adding revision history limit to 2
> [INFO] k8s: validating
> /home/claudio/alphaworks/projects/camel/.camel-jbang-run/http-log/target/classes/META-INF/jkube/kubernetes/http-log-deployment.yml
> resource
> [INFO] --- k8s:1.18.1:deploy (default-cli) @ http-log ---
> [INFO] k8s: Using Kubernetes at https://192.168.39.23:8443/ in namespace null
> with manifest
> /home/claudio/alphaworks/projects/camel/.camel-jbang-run/http-log/target/classes/META-INF/jkube/kubernetes.yml
> [INFO] k8s: Created Custom Resource: serving.knative.dev/v1#Service
> default/http-log
> [INFO] k8s: Creating a Deployment in default namespace with name http-log
> from kubernetes.yml
> [INFO] k8s: Created Deployment:
> target/jkube/applyJson/default/deployment-http-log.json
> [INFO] k8s: HINT: Use the command `kubectl get pods -w` to watch your pods
> start up
> {code}
> That in turn is merged with the knative service in the
> .camel-jbang-run/http-log/target/kubernetes/kubernetes.yml.
> There is no need for this deployment since in the kubernetes cluster, the
> knative operator controller will take care to create Deployment from the
> knative service custom resource.
> jkube maven plugin doesn't support knative
> We should find a way to skip the jkube maven plugin to generate the
> Deployment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
