[GitHub] [camel-k] squakez commented on issue #4179: Camel K 2.x upgrade 1.x strategy

["squakez (via GitHub)" <gi...@apache.org>]

squakez commented on issue #4179:
URL: https://github.com/apache/camel-k/issues/4179#issuecomment-1490434976

   > It is interesting [how syndesis upgraded to new versions](https://github.com/syndesisio/syndesis/blob/1.15.x/install/operator/pkg/syndesis/versions/versions.go).
   > 
   > It migrates the old custom resources to new one. This way the apis can be upgrade from v1alpha -> v1beta -> v1 -> ...
   
   Thanks for the link, was not aware of that in Syndesis. I'm right now looking to solve this problem as it finally we'll need to upgrade the `KameletBinding` to `Binding` CR type. However, I'm looking at https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#webhook-conversion which looks to be the official way in order to handle the conversion. In our case it should be easy enough as we only need to change the name of the resource.


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