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.

Sign up for GitHub

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

Add documentation re. init containers customization #3369

Merged
merged 1 commit into from
Jul 2, 2020
Merged

Add documentation re. init containers customization #3369

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions docs/orchestrating-elastic-stack-applications/customize-pods.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,34 @@ spec:

NOTE: APM Server configuration is identical to the Kibana configuration except for the `apiVersion` and `kind` fields.

The example below shows how it's also possible to customize the init containers created as part of the Pods to initialize the filesystem or to manage the keystores.

[source,yaml,subs="attributes,callouts"]
----
apiVersion: elasticsearch.k8s.elastic.co/{eck_crd_version}
kind: Elasticsearch
metadata:
name: quickstart
spec:
version: {version}
nodeSets:
- name: default
count: 3
podTemplate:
spec:
initContainers:
- name: elastic-internal-init-keystore
resources: # override the default resources set by the operator
limits:
cpu: 1000m
memory: 368Mi
requests:
cpu: 1000m
memory: 368Mi
secureSettings:
- secretName: es-secret
----

[float]
== More examples

Expand Down