squakez commented on issue #4618:
URL: https://github.com/apache/camel-k/issues/4618#issuecomment-1653114092
Sure. Right now, the operator is not deploying a Kamelet, but it transform
the Kamelet into a route template. For example:
```
k get cm timer-source-to-log-sink-kamelet-log-sink-template -o yaml
apiVersion: v1
data:
content: |
- routeTemplate:
from:
steps:
- to:
parameters:
level: '{{?level}}'
logMask: '{{?logMask}}'
marker: '{{?marker}}'
multiline: '{{?multiline}}'
showAllProperties: '{{?showAllProperties}}'
showBody: '{{?showBody}}'
showBodyType: '{{?showBodyType}}'
showCachedStreams: '{{?showCachedStreams}}'
showExchangePattern: '{{?showExchangePattern}}'
showHeaders: '{{?showHeaders}}'
showProperties: '{{?showProperties}}'
showStreams: '{{?showStreams}}'
uri: log:{{loggerName}}
uri: kamelet:source
id: log-sink
kind: ConfigMap
```
This is working, but I think that we need instead to deploy the Kamelet spec
and let the runtime to handle such Kamelet with the mechanism expected by the
framework.
Hope it clarifies.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
