You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/10/12 01:38:08 UTC

[GitHub] [apisix-ingress-controller] tao12345666333 opened a new issue #707: proposal: use a uniform CRD APIVersion

tao12345666333 opened a new issue #707:
URL: https://github.com/apache/apisix-ingress-controller/issues/707


   Currently in this project, we use different apiversions for management of different resources.
   However, the frequency of change of different resources is not the same, which leads to management confusion.
   
   E.g
   
   ApisixRoute -> v2beta2
   ApisixUpstream -> v1
   ApisixTls -> v1
   ApisixConsumer -> v2alpha1
   ApisixClusterConfig -> v2alpha1
   
   Users who are not familiar with this project may be confused about this, and because of the possible lag in the documentation, users may use the old version.
   
   This aspect will increase the user's learning cost. On the other hand, it will increase the maintenance cost of the project.
   We have to maintain mutual references of multiple resources in the code.
   
   So I propose to use a unified CRD apiversion.
   
   In order to achieve this, we can implement it step by step:`
   
   Introduce the `v2beta3` apiversion in the APISIX Ingress v1.4, unify all resources to this version, and deprecate all alpha version resources.
   
   Release `v2` apiversion in APISIX Ingress v1.5 and mark all beta versions as deprecated.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #707: proposal: use a uniform CRD APIVersion

Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #707:
URL: https://github.com/apache/apisix-ingress-controller/issues/707#issuecomment-940582074


   mail list discuss: 
   
   https://lists.apache.org/thread.html/r7f1d6037334d5558550ceaf79738ca421b6154b0b32854f9a331d1e9%40%3Cdev.apisix.apache.org%3E


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] gxthrj commented on issue #707: proposal: use a uniform CRD APIVersion

Posted by GitBox <gi...@apache.org>.
gxthrj commented on issue #707:
URL: https://github.com/apache/apisix-ingress-controller/issues/707#issuecomment-940583035


   Agree, The feature can reduce the cost of understanding.
   


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [apisix-ingress-controller] tao12345666333 commented on issue #707: proposal: use a uniform CRD APIVersion

Posted by GitBox <gi...@apache.org>.
tao12345666333 commented on issue #707:
URL: https://github.com/apache/apisix-ingress-controller/issues/707#issuecomment-1074707438


   Update:  
   
   I think we can drop the v2beta1 support when the v2 API version is introduced in v1.5. This makes the whole easier to maintain.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org