lsergio commented on issue #5179:
URL: https://github.com/apache/camel-k/issues/5179#issuecomment-1964077004
@squakez Here is an update with a few other scenarios:
**Scenario 1**
Quartz integration, Cron Trait configured with fallback:true
```
spec:
sources:
- name: flow1.groovy
content: |-
from('quartz://flow1/trigger?cron=0+*+*+?+*+*')
.to("https://httpbin.org/delay/2?bridgeEndpoint=true";)
.to("log:info")
traits:
cron:
fallback: true
```
**Results**
* Camel K created a deployment and not a CronJob (as expected)
* No Service or Knative Service/Revision was created (as expected)
* The deployment pod failed with the reported error
* Disabling the knative trait fixed the error
**Scenario 2**
Rest Integration, knatice-service trait disabled so the service is internal
to the cluster only
```
spec:
sources:
- name: flow1.groovy
content: |-
from('rest:GET:/demo')
.to("https://httpbin.org/delay/2?bridgeEndpoint=true";)
.to("log:info")
traits:
knative-service:
enabled: false
```
**Results**
* Camel K created a deployment and a ClusterIP Service (as expected)
* No Knative Service/Revision was created (as expected)
* The deployment pod failed with the reported error
* Disabling the knative trait fixed the error
**Scenario 3**
Rest Integration, knatice-service trait enabled so the service is exposed
with Knative
```
spec:
sources:
- name: flow1.groovy
content: |-
from('rest:GET:/demo')
.to("https://httpbin.org/delay/2?bridgeEndpoint=true";)
.to("log:info")
traits:
knative-service:
enabled: true
minScale: 1
```
**Results**
* Camel K created a Knative Service (as expected)
* Knative created 2 services: `basic-00001` and `basic-00001-private`
* The deployment pod failed with the reported error
* Knative revision status remained with Ready = Unknown and Reason =
Deploying
* Disabling the knative trait fixed the error, and it changed the number of
services Knative created: now there are `basic`, `basic-0001` and
`basic-00001-private` services.
So now I'm wondering if the Knative trait should play a role in scenarios
where a service is not created - scenarios 1 & 2. And trying to understand why
knative didn't create the 3 services in the 3rd scenario.
--
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.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
