Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

helm chart: Support K8S 1.8+ #141

Closed
mumoshu opened this issue Feb 2, 2018 · 5 comments
Closed

helm chart: Support K8S 1.8+ #141

mumoshu opened this issue Feb 2, 2018 · 5 comments

Comments

@mumoshu
Copy link
Contributor

mumoshu commented Feb 2, 2018

I have encountered docker-library/elasticsearch#111 after installing a cluster with helm.

Digging a bit, it turned out that K8S 1.8+ dropped support for annotation-based init containers so that the init container wasn't run at all in my env(K8S 1.9).

Rewriting the chart template to use an initContainers field rather than an annotation would fix the issue.

@mumoshu
Copy link
Contributor Author

mumoshu commented Feb 2, 2018

This and #138 seem to share the same cause.

@mumoshu
Copy link
Contributor Author

mumoshu commented Feb 2, 2018

Let me share what worked for me:

initContainers:
      - name: sysctl
        image: busybox
        imagePullPolicy: IfNotPresent
        command: ["sysctl", "-w", "vm.max_map_count=262144"]
        securityContext: { "privileged": true }
containers:
# snip

@mumoshu
Copy link
Contributor Author

mumoshu commented Feb 2, 2018

Turns out you'd better use the startup-script-daemonset approach than initContainers because the latter doesn't survive node restarts. See pires/kubernetes-elasticsearch-cluster#85

@stevesloka
Copy link
Member

I'm working on an update now to add the daemonset approach.

@stevesloka
Copy link
Member

Fixes in #149

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants