Hi, What is we are tying to do here? Are we trying to verify the ClientIP when exposing service via NodePort? IMO its working without issue.
On Sun, Feb 28, 2016 at 11:58 PM, Nishadi Kirielle <nish...@wso2.com> wrote: > Hi all, > > In order to test the session affinity in Kubernetes, I have deployed > WordPress on a kubernetes cluster with several replicas and enabled the > session affinity by setting service.spec.sessionAffinity to "ClientIP". > When the kubernetes service is exposed through NodePort, I have tested the > accuracy of session affinity using Apache bench mark for simple load > testing. With a load of 1000 requests and a maximum of 2 requests running > concurrently, all requests returned successfully without a failure. Thus > the session affinity is functioning properly when the services are exposed > via NodePort. > > The next attempt is to test the session affinity with ingress API exposing > the services. > > Any feedback or suggestions are highly appreciated. > > Thanks > > -- > *Nishadi Kirielle* > *Software Engineering Intern* > Mobile : +94 (0) 714722148 > Blog : http://nishadikirielle.blogspot.com/ > nish...@wso2.comm > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Lakmal Warusawithana Director - Cloud Architecture; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
