This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features 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
You can add any valid Elastic Maps Server setting as documented on the product page to the
The following example demonstrates how to set the log level to
apiVersion: maps.k8s.elastic.co/v1alpha1 kind: ElasticMapsServer metadata: name: quickstart spec: version: 7.15.1 count: 1 elasticsearchRef: name: "elasticsearch-sample" config: logging.level: debug
Alternatively, settings can be provided via a Secret specified in the
apiVersion: maps.k8s.elastic.co/v1alpha1 kind: ElasticMapsServer metadata: name: quickstart spec: version: 7.15.1 elasticsearchRef: name: elasticsearch-sample 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 and APM Server 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