Advanced configuration
editAdvanced configuration
editThis functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
If you already looked at the Elasticsearch on ECK documentation, some of these concepts might sound familiar to you. The resource definitions in ECK share the same philosophy when you want to:
- Customize the Pod configuration
- Customize the product configuration
- Manage HTTP settings
Elastic Maps Server configuration
editYou can add any valid Elastic Maps Server setting as documented on the product page to the spec.config
section.
The following example demonstrates how to set the log level to debug
:
apiVersion: maps.k8s.elastic.co/v1alpha1 kind: ElasticMapsServer metadata: name: quickstart spec: version: 8.15.3 count: 1 config: logging.level: debug
Alternatively, settings can be provided through a Secret specified in the configRef
element:
apiVersion: maps.k8s.elastic.co/v1alpha1 kind: ElasticMapsServer metadata: name: quickstart spec: version: 8.15.3 configRef: secretName: maps-config --- apiVersion: v1 kind: Secret metadata: name: maps-config stringData: elastic-maps-server.yml: |- logging.level: debug
Refer to Set compute resources for Kibana, Enterprise Search, Elastic Maps Server, APM Server and Logstash for adjusting compute resources for Elastic Maps Server.
Scale out an Elastic Maps Server deployment
editTo deploy more than one instance of maps, all the instances must mount the data volume containing the basemap read only. When this is the case, scaling out is just a matter of increasing the count
attribute.