On Tue, Jul 11, 2017 at 11:07 AM, Chamila De Alwis <[email protected]> wrote:
> Thanks Chamalee & Lakmal! > > > Regards, > Chamila de Alwis > Committer and PMC Member - Apache Stratos > Senior Software Engineer | WSO2 > Blog: https://medium.com/@chamilad > > > > On Tue, Jul 11, 2017 at 10:50 AM, Lakmal Warusawithana <[email protected]> > wrote: > >> >> When dynamic GWs created, adding proper domain into ingress (and then LB) >> will be able to access these GWs. >> >> > My question was regarding this. Name resolution and routing differs from > platform to platform, so how would they be handled? For example (as I > understand) > > 1. User selects Per API GW option and then publishes API > 2. Label assignment happens at API and GW instance level > 3. GW Service (ex: K8S) can be routed inside the cluster only > 4. For external routing, either an Ingress resource or Service > LoadBalancing should be used > > I'm still unclear how an API invocation would complete in this case. > Earlier the URL is generated with the Gateway LB Public DNS name. However > in this case, there will have to be multiple external-facing load balancers > that route traffic to Pods (ex: K8S) in a private network. Therefore, would > creating the above constructs (ingress for K8S) be handled by this feature > as well? Otherwise, per API deployment, there will have to be a manual > entry where either DNS or a connecting LB has to be modified. > Yes, we are handling Ingress in this feature as well. -- Lakmal Warusawithana Director - Cloud Architecture; WSO2 Inc. Mobile : +94714289692 Blogs : https://medium.com/@lakwarus/ http://lakmalsview.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
