+1 to use Fabric8 K8S client. A later version, 2.5.2 is now available on wso2/orbit.
Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Senior Software Engineer | WSO2 Blog: https://medium.com/@chamilad On Fri, Jul 28, 2017 at 10:13 AM, Dilan Udara Ariyaratne <[email protected]> wrote: > Hi Koshalya, > > Can you explain how the authentication and authorization happens in > between > the fabric8 kubernetes-client and any remote kubernetes cluster API Server > that we are hoping to connect ? > > Thanks, > Dilan. > > *Dilan U. Ariyaratne* > Senior Software Engineer > WSO2 Inc. <http://wso2.com/> > Mobile: +94766405580 <%2B94766405580> > lean . enterprise . middleware > > > On Thu, Jul 27, 2017 at 5:52 PM, Subhashinie Koshalya < > [email protected]> wrote: > >> Hi all, >> >> Currently at API publisher, the creator manually enters the backend >> service URI as the endpoint. In addition to the current capability, the >> idea is to let API Manager 3.0.0 support a "global endpoint" field which >> appears in the API Create UI, and be used for an external service discovery >> process to list out the available backend service endpoints within the >> tenant's scope. >> >> With the expectation of expanding the feature to multiple other >> platforms, initial plan is to make this work with Kubernetes. >> >> [image: ServiceD.jpeg] >> >> *As for Kubernetes the criteria would be labels. >> >> [image: servDisc.png] >> >> >> >> After discovery details listed in the UI will be, >> >> - >> >> service name >> - >> >> (eg: "external-example-service") >> - >> >> protocol + external IP with port or external name >> - >> >> (eg: http://146.148.47.155:3306 or https://example.domain.name) >> >> >> For a service endpoint to be discovered by the Publisher, >> >> - >> >> mainly it must have an external IP or external name >> - >> >> can be any of the "types" : ExternalName, LoadBalancer or NodePort >> >> >> Filtering will be possible according to, >> >> - >> >> Namespace >> - >> >> Labels >> >> >> We are hoping to use fabric8 in order to speak to the external >> Kubernetes cluster. >> >> We would like to have your feedback and suggestions in this regard. >> >> Links >> >> Kubernetes Services : >> >> https://kubernetes.io/docs/concepts/services-networking/service/ >> >> Thanks and regards, >> >> Subhashinie Koshalya >> Intern | Software Engineering >> WSO2, Inc. : http://wso2.com >> >> Email : [email protected] >> > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
