-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Elasticsearch 5.6.16 & Kubernetes 1.13.6 #162
Comments
Thanks for opening this. 1.13 just came out on GKE so I'm going to added it to the automated testing suite to see if there is anything else that breaks. |
Could you give me more information about your GKE setup? I wasn't able to reproduce this on a 1.13 cluster. I'm looking for the output of:
Here is the output from the cluster that I tested with:
|
@Crazybus Here is the one dev config where I was able to reproduce the issue.
|
I still can't reproduce it however the fix that you said worked is already being worked on in #171 |
#171 has been merged. Can you try with latest master to see if the issue is fixed for you? |
Seems good, thanks! |
@dcvtruong This is not 5.6.16 helm chart but the ES docker image version. |
Still fails for me:
panic: interface conversion: interface {} is string, not map[string]interface {} |
@zifeo Looks like you were able to install ES 5.6.16 image (docker.elastic.co) via helm chart to K8s 1.13.6
We have a couples of ES 5.4.x cluster running in VMs that need to be containerized and deploy to K8s cluster. |
Chart version: 7.1.1 (but image 5.6.16, major version 5)
Kubernetes version: 1.13.6
Kubernetes provider: GKE (Google Kubernetes Engine)
Helm Version: 2.14.1
helm get release
output -Describe the bug:
Upgrading to 1.13.6 from 1.12.x triggered Error caused by
can not run elasticsearch as root
Steps to reproduce:
Expected behavior:
Stable and usable cluster.
Provide logs and/or server output (if relevant): -
Any additional context:
The issue can be patched by adding a
runAsUser: 1000
here.The text was updated successfully, but these errors were encountered: