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 2020/09/04 05:49:00 UTC

[GitHub] [apisix] masahills opened a new issue #2165: request help: multi-tenancy/multi-workspace feature

masahills opened a new issue #2165:
URL: https://github.com/apache/apisix/issues/2165


   ### Issue description
   Hi,
   Do you have any plan to introduce multi-tenancy feature into APISIX?
   The motivation for this feature is that we want to let multiple internal organizations/teams to manage only their own configurations without affecting others. A concept of this feature is called 'Workspace' in Kong Enterprise Edition.


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



[GitHub] [apisix] moonming commented on issue #2165: request help: multi-tenancy/multi-workspace feature

Posted by GitBox <gi...@apache.org>.
moonming commented on issue #2165:
URL: https://github.com/apache/apisix/issues/2165#issuecomment-750715182


   yes.
   
   Thanks,
   Ming Wen
   Twitter: _WenMing
   
   
   罗泽轩 <no...@github.com> 于2020年12月24日周四 上午10:40写道:
   
   > @moonming <https://github.com/moonming>
   > I remember we move this feature to Enterprise version?
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > <https://github.com/apache/apisix/issues/2165#issuecomment-750712099>, or
   > unsubscribe
   > <https://github.com/notifications/unsubscribe-auth/AGJZBK76LMZSMSDLPOEIGNLSWKSYRANCNFSM4QXJDINA>
   > .
   >
   


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



[GitHub] [apisix] spacewander closed issue #2165: request help: multi-tenancy/multi-workspace feature

Posted by GitBox <gi...@apache.org>.
spacewander closed issue #2165:
URL: https://github.com/apache/apisix/issues/2165


   


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



[GitHub] [apisix] masahills edited a comment on issue #2165: request help: multi-tenancy/multi-workspace feature

Posted by GitBox <gi...@apache.org>.
masahills edited a comment on issue #2165:
URL: https://github.com/apache/apisix/issues/2165#issuecomment-689367235


   We have hundreds of internal API endpoints which go through a cluster of API gateway servers. It is a typical micro-service architecture and each API is developed and owned by different engineering teams within an organization.
   
   Managing all of those API configurations by a single devops team is not a realistic approach so we want each engineering team to manage their own API configurations with a proper account management (i.e. an internal IdP or Azule AD.)
   
   Since APISIX can update all API configurations without server restarts, it is a perfect solution for API management for micro-service architecture systems. I think this is a common requirement for organizations that use API gateway systems. For those users who need an API gateway, they usually have to control a large number of APIs from various sources with different polices and requirements. Managing those with a single devops team becomes nightmare as the number of configurations grows.
   
   I'm hoping that the feature is included in your roadmap sometime in the future. 


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



[GitHub] [apisix] masahills edited a comment on issue #2165: request help: multi-tenancy/multi-workspace feature

Posted by GitBox <gi...@apache.org>.
masahills edited a comment on issue #2165:
URL: https://github.com/apache/apisix/issues/2165#issuecomment-689367235






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



[GitHub] [apisix] moonming commented on issue #2165: request help: multi-tenancy/multi-workspace feature

Posted by GitBox <gi...@apache.org>.
moonming commented on issue #2165:
URL: https://github.com/apache/apisix/issues/2165#issuecomment-688590720


   There is no plan yet. Do you have a general plan for this?
    I am concern that this will increase the cost of user learning and use, not every user needs multi-tenancy.


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



[GitHub] [apisix] spacewander commented on issue #2165: request help: multi-tenancy/multi-workspace feature

Posted by GitBox <gi...@apache.org>.
spacewander commented on issue #2165:
URL: https://github.com/apache/apisix/issues/2165#issuecomment-750712099


   @moonming 
   I remember we move this feature to Enterprise version?


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



[GitHub] [apisix] masahills commented on issue #2165: request help: multi-tenancy/multi-workspace feature

Posted by GitBox <gi...@apache.org>.
masahills commented on issue #2165:
URL: https://github.com/apache/apisix/issues/2165#issuecomment-689367235


   We have hundreds of internal API endpoints which go through a cluster of API gateway servers. It is a typical micro-service architecture and each API is developed and owned by different engineering teams within an organization.
   
   Managing all of those API configurations by a single devops team is not a realistic approach so we want each engineering team to manage their own API configurations with a proper account management (i.e. an internal IdP or Azule AD.)
   
   Since APISIX can update all API configurations without server restarts, it is a perfect solution for API management for micro-service architecture systems. I think this is a common requirement for organizations that use an API gateway systems. Since those users who need an API gateway, they usually have to control a large number of APIs from various sources with different polices and requirements. Managing those with a single devops team becomes nightmare as the number of configurations grows.
   
   I'm hoping that the feature is included in your roadmap sometime in the future. 


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



[GitHub] [apisix] masahills edited a comment on issue #2165: request help: multi-tenancy/multi-workspace feature

Posted by GitBox <gi...@apache.org>.
masahills edited a comment on issue #2165:
URL: https://github.com/apache/apisix/issues/2165#issuecomment-689367235


   We have hundreds of internal API endpoints which go through a cluster of API gateway servers. It is a typical micro-service architecture and each API is developed and owned by different engineering teams within an organization.
   
   Managing all of those API configurations by a single devops team is not a realistic approach so we want each engineering team to manage their own API configurations with a proper account management (i.e. an internal IdP or Azule AD.)
   
   Since APISIX can update all API configurations without server restarts, it is a perfect solution for API management for micro-service architecture systems. I think this is a common requirement for organizations that use API gateway systems. For those users who need an API gateway, they usually have to control a large number of APIs from various sources with different polices and requirements. Managing those with a single devops team becomes nightmare as the number of configurations grows.
   
   I'm hoping that the feature is included in your roadmap sometime in the future. 


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