- Elastic Cloud on Kubernetes:
- Overview
- Quickstart
- Upgrading the Elastic Stack version
- Deploying ECK on OpenShift
- Accessing Elastic Stack services
- Managing compute resources
- Running Elasticsearch on ECK
- Pod Template
- JVM heap size
- Node configuration
- Volume claim templates
- HTTP settings & TLS SANs
- Virtual memory
- Custom HTTP certificate
- Settings managed by ECK
- Secure settings
- Custom configuration files and plugins
- Init containers for plugin downloads
- Update strategy
- Pod disruption budget
- Nodes orchestration
- Advanced Elasticsearch node scheduling
- Create automated snapshots
- Readiness probe
- Pod PreStop hook
- Running Kibana on ECK
- Running APM Server on ECK
- Creating custom images
- Configuring ECK
- Service meshes
- Managing licenses in ECK
- Troubleshooting
- Upgrading ECK
- Uninstalling ECK
- Glossary
- API Reference
- Release highlights
- Release notes
A newer version is available. For the latest information, see the
current release documentation.
Init containers for plugin downloads
editInit containers for plugin downloads
editYou can install custom plugins before the Elasticsearch container starts with an initContainer
. For example:
spec: nodeSets: - name: default count: 3 podTemplate: spec: initContainers: - name: install-plugins command: - sh - -c - | bin/elasticsearch-plugin install --batch repository-gcs
You can also override the Elasticsearch container image to use your own image with the plugins already installed, as described in the custom images doc. The snapshots document has more information on both these options. The Kubernetes document on init containers has more information on their usage as well.
The init container inherits the image of the main container image if one is not explicitly set. It also inherits the volume mounts as long as the name and mount path do not conflict. It also inherits the Pod name and IP address environment variables.
Was this helpful?
Thank you for your feedback.