- 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.
Settings managed by ECK
editSettings managed by ECK
editThe following Elasticsearch settings are managed by ECK:
-
cluster.name -
discovery.zen.minimum_master_nodes[7.0] Deprecated in 7.0. -
cluster.initial_master_nodes[7.0] Added in 7.0. -
network.host -
network.publish_host -
path.data -
path.logs -
xpack.security.authc.reserved_realm.enabled -
xpack.security.enabled -
xpack.security.http.ssl.certificate -
xpack.security.http.ssl.enabled -
xpack.security.http.ssl.key -
xpack.security.transport.ssl.certificate -
xpack.security.transport.ssl.enabled -
xpack.security.transport.ssl.key -
xpack.security.transport.ssl.verification_mode
While ECK does not prevent you from setting any of these settings yourself, you are strongly discouraged from doing so and we cannot offer support for any user provided Elasticsearch configuration that does use any of these settings.
Was this helpful?
Thank you for your feedback.