Details
-
Bug
-
Resolution: Done
-
Blocker
-
2021-M2
-
None
-
False
-
False
-
%
-
Undefined
Description
I am playing with the OLM operator upgrade and the Camel-K upgrade features. I created a new CatalogSource with its HEAD pointing to Camel-K TP2 release and installed Camel-K using OLM. Then I started new test integration.
//install Camel-K using OLM oc get csv NAME DISPLAY VERSION REPLACES PHASE red-hat-camel-k-operator.v1.2.1 Red Hat Integration - Camel K 1.2.1 Succeeded oc get IntegrationPlatform -o yaml | grep version f:version: {} version: 1.2.0 kamel init test.yaml kamel run test.yaml | grep version f:version: {} version: 1.2.0
Then I manually edited the image in the test CatalogSource (HEAD is pointing to the TP3 release). This step started the automatic upgrade of the operator. I was watching CSVs, and Integrations resources during the upgrade.
oc get csv -w NAME DISPLAY VERSION REPLACES PHASE red-hat-camel-k-operator.v1.2.1 Red Hat Integration - Camel K 1.2.1 Succeeded red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 red-hat-camel-k-operator.v1.2.1 Red Hat Integration - Camel K 1.2.1 Replacing red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 Pending red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 Pending red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 InstallReady red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 InstallReady red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 Installing red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 Installing red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 Installing red-hat-camel-k-operator.v1.3.0 Red Hat Integration - Camel K 1.3.0 red-hat-camel-k-operator.v1.2.1 Succeeded red-hat-camel-k-operator.v1.2.1 Red Hat Integration - Camel K 1.2.1 Deleting red-hat-camel-k-operator.v1.2.1 Red Hat Integration - Camel K 1.2.1 Deleting
➜ ~ oc get integration -w
NAME PHASE KIT REPLICAS
test Running kit-c15ilvpqujklhu172mvg 1
test Initialization
test Building Kit
test Building Kit kit-c15ip4cq2p7s25hc0p20
test Deploying kit-c15ip4cq2p7s25hc0p20
test Running kit-c15ip4cq2p7s25hc0p20
test Running kit-c15ip4cq2p7s25hc0p20 0
test Running kit-c15ip4cq2p7s25hc0p20 1
oc get integration test -o yaml | grep version
f:version: {}
version: 1.3.0
The integration is apparently immediately rebuilt. This could be problematic because it can cause unwanted service outages on the customer's side and in the worst case, the integration would not be able to run with the new version and the service would die totally. I thought we aim to keep all integration running and wait for `kamel rebuild` command.
