Advanced configuration for Elastic Maps Server on Elastic Cloud on Kubernetes

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

You 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: 9.5.6
  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: 9.5.6
  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, Elastic Maps Server, APM Server and Logstash for adjusting compute resources for Elastic Maps Server.

To 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.