Exether opened a new issue, #6464:
URL: https://github.com/apache/camel-k/issues/6464
### Bug description
Hello,
I'm testing our integrations with 2.9.0 and I noticed a regression on how
configmap and secret are mounted.
Consider the following objects:
`
apiVersion: v1
data:
project.properties: |
local.property1=value1
local.property2=value2
kind: ConfigMap
metadata:
name: itg.project.default.configuration
---
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
annotations:
camel.apache.org/operator.id: camel-k
creationTimestamp: null
name: basic-route
spec:
flows:
- route:
from:
steps:
- setBody:
simple: Test 1
- to:
uri:
log:integrations.example.ConfigMap?level=INFO&showHeaders=true&showBody=true&showProperties=true
uri: timer:java?period=55000
id: basic-route
traits:
mount:
configs:
- configmap:itg.project.default.configuration
status: {}
`
The integration will start fine in camel-k 2.8.0 but fail with 2.9.0
(doesn't start because it can't find configmap).
Having a look at the corresponding deployment we see that the issue comes
from the fact 2.9.0 is using an incorrect reference to the configmap (left
2.8.0 / right 2.9.0):
<img width="1403" height="426" alt="Image"
src="https://github.com/user-attachments/assets/3040ae03-4965-4900-9063-669993d59dcb";
/>
### Camel K or runtime version
2.9.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]
