[GitHub] [camel-k] nicolaferraro commented on issue #921: Moving api to v1

[GitBox <gi...@apache.org>]

nicolaferraro commented on issue #921: Moving api to v1
URL: https://github.com/apache/camel-k/issues/921#issuecomment-566478311
 
 
   We can set versions like this:
   ```
     versions:
       - name: v1alpha1
         served: true
         storage: false
       - name: v1
         served: true
         storage: true
   ```
   
   It means that we store resources in version `v1` but also clients using `v1alpha1` will still continue to work (e.g. Knative Camel Sources and others).
   
   This change assumes that there are no changes between `v1alpha1` and `v1`. The alternative is to adding mutating webhooks, which complicates too much the deployment.
   Since we're moving from alpha to stable, I'd do minor changes without caring about conversion (mentioning possible minor changes in release notes).
   
   I'd migrate **all** APIs to `v1` because `Integration` and `IntegrationPlatform` are pretty stable and all the others are internal APIs and people should not care a lot about their stability.
   
   I'd do all changes after other big PRs are merged.. doing some tests now.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services