- 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.
HTTP settings & TLS SANs
editHTTP settings & TLS SANs
editIn the spec.http.service.spec
section, you can change the Kubernetes service used to expose Elasticsearch:
spec: http: service: spec: type: LoadBalancer
Check the Kubernetes Publishing Services (ServiceTypes) that are currently available.
You can add an IP or a DNS name in the SAN of the self-signed certificate configured by default to secure the HTTP layer with TLS in the spec.http.tls.selfSignedCertificate
section.
spec: http: tls: selfSignedCertificate: subjectAltNames: - ip: 1.2.3.4 - dns: hulk.example.com
Was this helpful?
Thank you for your feedback.