Hi Chamalee On Tue, Jul 11, 2017 at 1:11 AM, Chamalee De Silva <[email protected]> wrote:
> Hi Nuwan, > Thanks for pointing that out. > As I first mentioned in this thread, we will provide an extension point in > this feature to support other container based management systems as well > without limiting to Kubernetes and Openshift. > Yes, I saw that. but thats not my point. In the above design we have made an assumption whoever wants to use this feature need to have some kind of a CMS. I think thats a mistake and we are limiting the potential of this feature if we do it that way. What if someone want to just deploy a gateway in a traditional VM with a single API ? One step above this would be to provide a dockerized version and the most integrated version of it is directly pushing to some CMS. If we provide the artifacts thats needed to deploy the gateway and the api definition, the user has the flexibility to decide where and how he wants to deploy. We can ofcause provide OOTB integration to k8s/openshift but thats icing. Regards, /Nuwan > I will take this into consideration when implementing. > > > On Tue, Jul 11, 2017 at 7:54 AM, Chamila De Alwis <[email protected]> > wrote: > >> +1 >> >> IMO users wouldn't always be willing to start with a Container Cluster >> Management system and limiting this feature to a few would limit their >> chances to properly make use of the feature. >> >> From the above explanation, I didn't yet understand how routing would >> happen in a CMS when separate Gateways are deployed as separate services. >> For example, if we take K8S, how would the API endpoint be mapped to a >> Service or Service Loadbalancer endpoint? >> > > @Chamila, > Thanks for the response. > > Answeing your question, > Here we are using the Label resource in API Manager. > > In API Manager 3.0.0, When creating an API we can select labels for the > API. > When setting up gateways for API Manager also we need to register the > gateways with a label and the access URL of the gateway. > > With this feature what we do is auto-generate a label for the API and > publish it. Then with the same label, we start up a gateway in CMS ( e.g. > K8 ). > So for K8s we are using the same label which is auto-generated, as the > label for the deployment (replicas) and as the selector for the service to > receive traffic. > This newly created gateway is registered in API Manager with this label > and the URL of the Service (Service Load Balancer Endpoint). > So we have the {gateway_URL} which we can use to construct the API > endpoint from API Manager side. > > For k8s and openshift this is the design that we discussed. > > > I will further check on how we can get the API Access URL with the other > CMS as Nuwan mentioned. > > > Thanks, > Chamalee > > > -- > Thanks & Regards, > > *Chamalee De Silva* > Software Engineer > *WS**O2* Inc. :http://wso2.com/ > > Office :- *+94 11 2145345 <%2B94%2011%202145345>* > mobile :- *+94 7 <%2B94%2077%202782039>1 4315942* > > -- *Thanks & Regards,* *Nuwan Bandara | Director - **Solutions Architecture, WSO2 Inc.* *+1 646 643 8618 | +1 650 745 2169 Ext 4212 | http://nuwanbando.com <http://nuwanbando.com> * <http://www.nuwanbando.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
