squakez opened a new issue, #5491:
URL: https://github.com/apache/camel-k/issues/5491
### What happened?
Verified when upgrading from Camel version 2.3.0 to 2.3.1. Any existing
integration is restarted and even a new Pod is scheduled (see log above). It is
very likely because we use the operator version to calculate digest (see #5192)
when we really should account for runtime version/provider instead.
```
NAME PHASE RUNTIME PROVIDER RUNTIME VERSION KIT
REPLICAS
# Camel K 2.3.0
test Building Kit quarkus 3.8.1
kit-couff1l2cjmc73fhht0g
test Deploying quarkus 3.8.1
kit-couff1l2cjmc73fhht0g
test Running quarkus 3.8.1
kit-couff1l2cjmc73fhht0g 0
test Running quarkus 3.8.1
kit-couff1l2cjmc73fhht0g 1
test Running quarkus 3.8.1
kit-couff1l2cjmc73fhht0g 1
# Camel K 2.3.1 upgrade
test Running quarkus 3.8.1
kit-couff1l2cjmc73fhht0g 1
test Running quarkus 3.8.1
kit-couff1l2cjmc73fhht0g 2
test Running quarkus 3.8.1
kit-couff1l2cjmc73fhht0g 1
test Running quarkus 3.8.1
kit-couff1l2cjmc73fhht0g 1
```
The rebuild should only be performed manually.
### Steps to reproduce
_No response_
### Relevant log output
_No response_
### Camel K version
_No response_
--
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]
