You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/05/23 09:02:07 UTC
[GitHub] [camel-k] squakez opened a new issue, #3294: Integration upgraded automatically after operator upgrade
squakez opened a new issue, #3294:
URL: https://github.com/apache/camel-k/issues/3294
Just tested with the following scenario:
1. Use an operator version (ie, 1.8)
2. Run a sample Integration
3. Upgrade the operator version (ie, 1.9)
The Integration on point 2 is rebuilt automatically (is that correct behavior?) And, even if that would be correct, the resulting Integration has still the previous operator version parameters, ie:
```
status:
...
phase: Running
platform: camel-k
profile: Kubernetes
replicas: 1
runtimeProvider: quarkus
runtimeVersion: 1.12.0
selector: camel.apache.org/integration=sample
version: 1.8.2
```
--
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-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3294: Integration upgraded automatically after operator upgrade
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3294:
URL: https://github.com/apache/camel-k/issues/3294#issuecomment-1183072810
It does not happen upgrading from `1.9` to `1.10`(nightly). Probably it was fixed by other developments.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez closed issue #3294: Integration upgraded automatically after operator upgrade
Posted by GitBox <gi...@apache.org>.
squakez closed issue #3294: Integration upgraded automatically after operator upgrade
URL: https://github.com/apache/camel-k/issues/3294
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] squakez commented on issue #3294: Integration upgraded automatically after operator upgrade
Posted by GitBox <gi...@apache.org>.
squakez commented on issue #3294:
URL: https://github.com/apache/camel-k/issues/3294#issuecomment-1134390270
@astefanutti do you remind if the automatic rebuild was an intentional behavior?
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on issue #3294: Integration upgraded automatically after operator upgrade
Posted by GitBox <gi...@apache.org>.
astefanutti commented on issue #3294:
URL: https://github.com/apache/camel-k/issues/3294#issuecomment-1142059912
@squakez I don't think so, the rebuild should only be triggered by manually running `kamel rebuild`.
--
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-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org