Deploy ECK on Openshift
Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECK
Generally available
This section shows how to run ECK on OpenShift.
- Before you begin
- Deploy the operator
- Deploy an Elasticsearch instance with a route
- Deploy a Kibana instance with a route
- Grant privileged permissions to Beats
- Grant host access permission to Elastic Agent
To run the instructions on this page, you must be a
system:adminuser or a user with the privileges to create Projects, CRDs, and RBAC resources at the cluster level.Set virtual memory settings on the Kubernetes nodes.
Before deploying an Elasticsearch cluster with ECK, make sure that the Kubernetes nodes in your cluster have the correct
vm.max_map_countsysctl setting applied. By default, Pods created by ECK are likely to run with therestrictedSecurity Context Constraint (SCC) which restricts privileged access required to change this setting in the underlying Kubernetes nodes.Alternatively, you can opt for setting
node.store.allow_mmap: falseat the Elasticsearch node configuration level. This has performance implications and is not recommended for production workloads.For more information, check Virtual memory.