venom90 opened a new issue, #5313:
URL: https://github.com/apache/camel-k/issues/5313
### What happened?
When deploying a Camel K integration with specified annotations for enabling
and configuring the dapr.io sidecar, the annotations do not appear to be
applied to the resulting pod. This issue prevents the Dapr sidecar from being
correctly configured and attached to the Camel K integration pod.
**Environment**
Camel K Version: Camel K Client 2.2.0
Kubernetes Version: Kubernetes 1.29.1-do.0
Dapr Version: Runtime version: 1.13.1
Installation Method: kamel CLI
Cluster Type: DigitalOcean Managed Kubernetes
### Steps to reproduce
## 1. Created a ConfigMap with the following content to specify dapr.io
annotations:
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: camelk-integration-config
data:
integration.properties: |
camel.k.pod.annotation.dapr.io/enabled=true
camel.k.pod.annotation.dapr.io/app-id=helloapp
camel.k.pod.annotation.dapr.io/config=tracing
```
## 2.Applied the ConfigMap to the Kubernetes cluster.
## 3. Deployed the Camel K integration using the following command:
```bash
kamel run hello.js --config configmap:camelk-integration-config
```
## 4. Checked the deployed pod annotations using:
```bash
kubectl describe pod <pod-name>
```
### Relevant log output
```shell
{"level":"info","ts":"2024-03-31T18:55:20Z","logger":"camel-k.cmd","msg":"v1apha1.KameletBinding
is deprecated, please, use v1.Pipe instead"}
```
### Camel K version
2.2.0
--
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]
