Deploy ECK on OpenShift

This page shows how to run ECK on OpenShift.

Docker images of the APM Server before 7.9 are compatible with the restricted Security Context Constraint. To run the APM Server on OpenShift you must allow the Pod to run with the anyuid SCC as described in Deploy an APM Server instance with a route

To run the instructions on this page, you must be a system:admin user 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_count sysctl setting applied. By default, Pods created by ECK are likely to run with the restricted Security 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: false at the Elasticsearch node configuration level, but note that this has performance implications and is not recommended for production workloads.

For more information, see: Virtual memory.