- 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.
Secure settings
editSecure settings
editYou can specify secure settings with Kubernetes secrets. The secrets should contain a key-value pair for each secure setting you want to add. ECK automatically injects these settings into the keystore on each Elasticsearch node before it starts Elasticsearch.
spec: secureSettings: - secretName: one-secure-settings-secret - secretName: two-secure-settings-secret
You can export a subset of secret keys and also project keys to specific paths using the entries
, key
and path
fields:
spec: secureSettings: - secretName: your-secure-settings-secret entries: - key: key1 - key: key2 path: newkey2
See How to create automated snapshots for an example use case.
Was this helpful?
Thank you for your feedback.