+1 for the proposed approach. I will stick to the other thread.
Thanks
On Mon, Mar 14, 2016 at 10:00 AM, Imesh Gunaratne wrote:
>
>
> On Sun, Mar 13, 2016 at 11:37 PM, Nishadi Kirielle
> wrote:
>
>> Hi Imesh,
>> The reason for choosing SSL termination over
On Sun, Mar 13, 2016 at 11:37 PM, Nishadi Kirielle wrote:
> Hi Imesh,
> The reason for choosing SSL termination over SSL pass through is due to
> the complexity of handling separate SSL certificates for each servers
> behind the load balancer in kubernetes cluster. As in App
Hi Imesh,
The reason for choosing SSL termination over SSL pass through is due to the
complexity of handling separate SSL certificates for each servers behind
the load balancer in kubernetes cluster. As in App Cloud the kubernetes
cluster is not direcctly exposed and the communication between the
On Thu, Mar 10, 2016 at 1:28 PM, Nishadi Kirielle wrote:
> Thank you for the suggestion of using the default self signed certificate.
> I have attempted SSL termination approach of terminating the SSL
> connection at the load balancer and sending unencrypted connections to the
Thank you for the suggestion of using the default self signed certificate.
I have attempted SSL termination approach of terminating the SSL connection
at the load balancer and sending unencrypted connections to the backend
server via the ha proxy configuration of 'ssl verify none'. This approach
On Thu, Mar 10, 2016 at 10:49 AM, Nishadi Kirielle wrote:
> Hi all,
> I have only tested for http traffic earlier. Although the kubernetes
> service loadbalancer template has support for https, when I have deployed
> an application ( dell/tomcat ) which has the support for
Hi all,
I have only tested for http traffic earlier. Although the kubernetes
service loadbalancer template has support for https, when I have deployed
an application ( dell/tomcat ) which has the support for https, the ha
proxy load balancer did not identify it as a https service in the haproxy
Hi Deep,
On Tue, Mar 8, 2016 at 8:08 PM, Deependra Ariyadewa wrote:
>
> On Mon, Mar 7, 2016 at 10:30 AM, Nishadi Kirielle
> wrote:
>
>> Hi All,
>> I have written the blog post on load balancing and session affinity in
>> kubernetes. [1]
>>
>
> I am going test
On Mon, Mar 7, 2016 at 10:30 AM, Nishadi Kirielle wrote:
> Hi All,
> I have written the blog post on load balancing and session affinity in
> kubernetes. [1]
>
I am going test session affinity for HTTPS triffic in Kubernetes following
your configurations. Did you try to enable
Hi All,
I have written the blog post on load balancing and session affinity in
kubernetes. [1]
Thank you
[1].
http://nishadikirielle.blogspot.com/2016/03/load-balancing-kubernetes-services-and.html
On Fri, Mar 4, 2016 at 8:22 PM, Nishadi Kirielle wrote:
> Thanks a lot. I
Thanks a lot. I will write a blog post and share it.
Thanks
On Fri, Mar 4, 2016 at 6:07 PM, Sagara Gunathunga wrote:
>
> Great, it would be better if Nishadi can write a step by step blog post
> about how to do this. We had to do a 30 hours hackathon to change MSF4J
>
Great, it would be better if Nishadi can write a step by step blog post
about how to do this. We had to do a 30 hours hackathon to change MSF4J
Pet-store sample due to this issue :)
Thanks !
On Fri, Mar 4, 2016 at 5:54 PM, Imesh Gunaratne wrote:
> Indeed! Overall great effort!!
Indeed! Overall great effort!!
Thanks
On Fri, Mar 4, 2016 at 3:36 PM, Lakmal Warusawithana
wrote:
> Great work Nishadi!
>
> On Fri, Mar 4, 2016 at 3:34 PM, Nishadi Kirielle wrote:
>
>> Hi all,
>> In attempting to configure session affinity in kubernetes load
Great work Nishadi!
On Fri, Mar 4, 2016 at 3:34 PM, Nishadi Kirielle wrote:
> Hi all,
> In attempting to configure session affinity in kubernetes load balancing,
> I tried to run nginx alpha ingress controller[1] to expose the services
> through ingress. But the generated
Hi all,
In attempting to configure session affinity in kubernetes load balancing, I
tried to run nginx alpha ingress controller[1] to expose the services
through ingress. But the generated nginx configuration file were missing
the service ports to access the services. Thus I have manually updated
On Mon, Feb 29, 2016 at 12:12 PM, Lakmal Warusawithana
wrote:
>
>
> On Mon, Feb 29, 2016 at 11:56 AM, Imesh Gunaratne wrote:
>
>> Hi Lakmal,
>>
>> On Mon, Feb 29, 2016 at 11:37 AM, Lakmal Warusawithana
>> wrote:
>>
>>> Hi,
>>>
>>> What is we
On Mon, Feb 29, 2016 at 11:56 AM, Imesh Gunaratne wrote:
> Hi Lakmal,
>
> On Mon, Feb 29, 2016 at 11:37 AM, Lakmal Warusawithana
> wrote:
>
>> Hi,
>>
>> What is we are tying to do here? Are we trying to verify the ClientIP
>> when exposing service via NodePort?
Hi Lakmal,
On Mon, Feb 29, 2016 at 11:37 AM, Lakmal Warusawithana
wrote:
> 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.
>
> Yes the first step was to verify ClientIP and then
On Mon, Feb 29, 2016 at 11:12 AM, Nishadi Kirielle wrote:
> In order to verify session affinity, I have created three replicas of
> wordpress. With the first request I have created a user and logged into
> wordpress. As per your suggestion in the load testing with Apache
>
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 wrote:
> Hi all,
>
> In order to test the session affinity in Kubernetes, I have
Hi,
I tried testing this with v1.1.2. You can access this still with this IP
192.168.58.228.
At that time there were few problems with session affinity.
*How I test:*
I created a session variable and incremented it if session already exist.
In addition printed the ip of the pod.
My observation
In order to verify session affinity, I have created three replicas of
wordpress. With the first request I have created a user and logged into
wordpress. As per your suggestion in the load testing with Apache
Benchmark, I have given an internal link of my logged in profile. If the
session affinity
Hi Nishadi,
On Sun, Feb 28, 2016 at 11:58 PM, Nishadi Kirielle 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
I have used pires/kubernetes-vagrant-coreos-cluster setup for this testing
which uses Kubernetes 1.1.7.
Thanks
On Mon, Feb 29, 2016 at 8:59 AM, Chamila De Alwis wrote:
> Hi Nishadi,
>
> What was the Kubernetes version this test was executed?
>
>
> Regards,
> Chamila de Alwis
Hi Nishadi,
What was the Kubernetes version this test was executed?
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sun, Feb 28, 2016 at 11:58 PM, Nishadi Kirielle wrote:
> Hi
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
26 matches
Mail list logo