You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "gansheer (via GitHub)" <gi...@apache.org> on 2023/03/24 08:27:04 UTC

[GitHub] [camel-k] gansheer opened a new issue, #4160: Kamel cli reset/uninstall --all does not clean the camelcatalog

gansheer opened a new issue, #4160:
URL: https://github.com/apache/camel-k/issues/4160

   Using the client kamel to remove the operator with the commands `kamel reset` then `kamel uninstall --all` does not remove the camel catalog CR.
   It contains a status referencing the builder container availability:
   ```yaml
   status:
     conditions:
     - lastTransitionTime: "2023-03-24T08:17:03Z"
       lastUpdateTime: "2023-03-24T08:17:03Z"
       message: Container image successfully built
       reason: Builder Image
       status: "True"
       type: Ready
     image: 10.109.132.152/default/camel-k-runtime-quarkus-builder:3.20.1-snapshot
     observedGeneration: 1
     phase: Ready
   ```
   
   When installing new code with `kamel install` on the same kubernetes cluster, the camel catalog CR still exists. The effect is that the builder container is not rebuild by the camel-k operator.
   
   I suggest we remove the camel catalog in the `kamel uninstall --all`. Anything that is against that modification in the new builder design @squakez ?


-- 
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] gansheer commented on issue #4160: Kamel cli reset/uninstall --all does not clean the camelcatalog

Posted by "gansheer (via GitHub)" <gi...@apache.org>.
gansheer commented on issue #4160:
URL: https://github.com/apache/camel-k/issues/4160#issuecomment-1482459840

   I am on it :).


-- 
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 #4160: Kamel cli reset/uninstall --all does not clean the camelcatalog

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #4160:
URL: https://github.com/apache/camel-k/issues/4160#issuecomment-1482454486

   Thanks for reporting. Yes, I think the problem is that we leave `CamelCatalog`s in the cluster. Therefore, at next installation, the catalogs are still there. As for the builder, we detect when it's a snapshot and in such case we rebuild, but, since the catalog is "ready", then, it is not initialized, leaving the one previously installed. It makes sense to include the removal in the uninstall. @gansheer is it something you can take care of?


-- 
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 #4160: Kamel cli reset/uninstall --all does not clean the camelcatalog

Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #4160: Kamel cli reset/uninstall --all does not clean the camelcatalog
URL: https://github.com/apache/camel-k/issues/4160


-- 
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