# Kibana 6.8.2 deploying on K8S ( using security xpack feature )
**URL:** https://discuss.elastic.co/t/kibana-6-8-2-deploying-on-k8s-using-security-xpack-feature/197111
**Category:** Kibana
**Tags:** elastic-stack-security, docker
**Created:** [August 28, 2019, 12:18pm UTC](https://discuss.elastic.co/t/kibana-6-8-2-deploying-on-k8s-using-security-xpack-feature/197111 "2019-08-28T12:18:42Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@KingChooChoo](https://discuss.elastic.co/u/KingChooChoo)
#### Post date: [August 28, 2019, 12:18pm UTC](https://discuss.elastic.co/t/kibana-6-8-2-deploying-on-k8s-using-security-xpack-feature/197111/1 "2019-08-28T12:18:42Z")
Hi everyone ,
My name is Larry , I've been using **ELK stack** for 2 years and I'm enjoying a lot this platform . I've earned a lot of useful experience , that helps me to ease all procedures of logging for developers .
Not so long ago I decided to deploy my **Logstash** and **Kibana** services on **Kubernetes** , but then I've been caught by a little problem .
Problem : I want to use 2 pods ( to provide load balancing ) of **Kibana** with the _security feature_ , but when I try to log in it redirects me to a "Log In" page without any "errors".
I'm using images of **Logstash** 6.8.2 , **Kibana** 6.8.2 and Elastic cluster is distributed on VMs , all the stack worked perfect , but then I decided to add _xpack security feature_ and found out that I can't use 2 pods of **Kibana** in the same Deployment at the same moment . After that I tried to use only 1 pod and it works as it supposed to work , I also checked presence of conflicts between VM + container ... there is no problem , tried to add configuration of session affinity in _ClusterIP_ service and it didn't help . I guess that the problem is in my **K8S** configuration and I'm close to success , but it's not enough .
Thank you for all the support ! I hope I'm not at the dead end and I'll be able to solve my problem with your help ❤
P.S.: If there is no solution I'm glad to get feedback about your best practice of working with **ELK on K8S**.
---
### Author:  [@ikakavas](https://discuss.elastic.co/u/ikakavas)
#### Post date: [August 28, 2019, 1:09pm UTC](https://discuss.elastic.co/t/kibana-6-8-2-deploying-on-k8s-using-security-xpack-feature/197111/2 "2019-08-28T13:09:49Z")
> [@KingChooChoo](#):
>
> Problem : I want to use 2 pods ( to provide load balancing ) of **Kibana** with the _security feature_ , but when I try to log in it redirects me to a "Log In" page without any "errors".
Can you explain in detail what happens ? When you try to login at which of the two Kibanas ? Does one work and the other doesn't ? Do you enter your username and password and just get redirected to the login page again _without_ any errors ? What is written in the logs ?
When you use multiple kibana instances talking to the same elasticsearch cluster, you need to make sure that `xpack.security.encryptionKey` in kibana.yml is set to the same value in all your kibana instances. Otherwise, when you authenticate with kibana 1 and then at some point your LB sends you to kibana 2, it will not be able to read your session cookie and treat you as unauthenticated user.
> [@KingChooChoo](#):
>
> I'm glad to get feedback about your best practice of working with **ELK on K8S**.
Have you looked into our [ECK](https://www.elastic.co/blog/introducing-elastic-cloud-on-kubernetes-the-elasticsearch-operator-and-beyond) ?
---
### Author:  [@KingChooChoo](https://discuss.elastic.co/u/KingChooChoo)
#### Post date: [August 28, 2019, 2:58pm UTC](https://discuss.elastic.co/t/kibana-6-8-2-deploying-on-k8s-using-security-xpack-feature/197111/3 "2019-08-28T14:58:06Z")
Thank you for your attention , Ioannis .
I configured Elastic with xpack.security, elastic-setup-passwords and gave Kibana its elastic.username and elastic.password ( checked that VM works and 1 pod in K8S works ) and the only problem is 2 pods in K8S .
I connect with the Ingress URL to Kibana service ( I don't really know which pod is used ) and after entering the username and password I'm redirected to a clear "Log In" page to enter my username and password again without getting error of "wrong username / password " or something , and in pods I get logs of :
```auto
{"type":"response","@timestamp":"2019-08-28T12:01:57Z","tags":[],"pid":1,"method":"get","statusCode":200,"req":{"url":"/login?next=%2Fstatus","method":"get","headers":{"host":"< ***my pod IP*** >:5601","user-agent":"kube-probe/1.13","referer":"http://< ***my pod IP*** >:5601/status","accept-encoding":"gzip","connection":"close"},"remoteAddress":"< ***my remote address*** >","userAgent":"<***my remote agent ( same as address )***>","referer":"http://< ***my pod IP*** >:5601/status"},"res":{"statusCode":200,"responseTime":9,"contentLength":9},"message":"GET /login?next=%2Fstatus 200 9ms - 9.0B"}
```
I'll check the ECK , thanks . It also can help me to know your opinion if it's worth to use 2 ( or more ) pods to LoadBalance the Kibana , or 1 pod is enough to get a good performance .
---
### Author:  [@KingChooChoo](https://discuss.elastic.co/u/KingChooChoo)
#### Post date: [September 1, 2019, 10:24am UTC](https://discuss.elastic.co/t/kibana-6-8-2-deploying-on-k8s-using-security-xpack-feature/197111/4 "2019-09-01T10:24:20Z")
Greetings , Ioannis !
I just wanted to say , that the problem was really with cookies and the line of xpack.security.encryptionKey solved this .
Thank you very much , I couldn't reply you earlier to say how much you helped me 😄
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 29, 2019, 10:34am UTC](https://discuss.elastic.co/t/kibana-6-8-2-deploying-on-k8s-using-security-xpack-feature/197111/5 "2019-09-29T10:34:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.