- Elastic Docs/
- Deploy and manage/
- Deploy/
- Elastic Cloud on Kubernetes/
- Orchestrate other Elastic applications/
- Elastic Maps Server
Deploy Elastic Maps Server
This 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.
Deploying Elastic Maps Server can be done with a simple manifest:
apiVersion: maps.k8s.elastic.co/v1alpha1kind: ElasticMapsServermetadata: name: quickstartspec: version: 9.3.0 count: 1Versions of Elastic Maps Server prior to 7.14 need a connection to Elasticsearch to verify the installed license. You define the connection with theelasticsearchRef attribute:
apiVersion: maps.k8s.elastic.co/v1alpha1kind: ElasticMapsServermetadata: name: quickstartspec: version: 7.13 count: 1 elasticsearchRef: name: quickstart namespace: defaultThe use ofnamespace is optional if the Elasticsearch cluster is running in the same namespace as Elastic Maps Server.
Any Elastic Maps Server can reference (and thus access) any Elasticsearch instance as long as they are both in namespaces that are watched by the same ECK instance. ECK will copy the required Secret from Elasticsearch to the Elastic Maps Server namespace. Elastic Maps Server cannot automatically connect to Elasticsearch (throughelasticsearchRef) in a namespace managed by a different ECK instance. For more information, checkRestrict cross-namespace resource associations.
The Elastic Maps Server configuration file is automatically setup by ECK to establish a secure connection to Elasticsearch.