CNE GCP Ready: Using Elasticsearch

Cloud Native Experience (CNE) GCP Ready environments use Elasticsearch for search workloads.

The platform deploys Elasticsearch in-cluster using Elastic Cloud on Kubernetes (ECK). Unlike AWS environments, GCP environments do not provision a managed OpenSearch service.

Elasticsearch Architecture

CNE GCP Ready deploys

• The ECK operator in the elastic-system namespace

• One or more Elasticsearch nodes inside the cluster

• Kubernetes resources managed through ECK custom resources

The ECK operator manages

• Elasticsearch lifecycle operations

• Certificates and TLS configuration

• StatefulSets and persistent storage

• Cluster upgrades and health management

Configure the ECK Operator

Configure the operator in system/infrastructure-provider.yaml.

Example:

eck-operator:
   resources:
      limits:
         cpu: 1000m
         memory: 1Gi

For supported configuration options, see Elastic Cloud on Kubernetes.

Configure Elasticsearch

Configure Elasticsearch in your environment’s infrastructure.yaml file.

search:
   elasticsearch:
      nodeCount: 3
      resources:
         limits:
            cpu: 2000m
            memory: 16Gi
         requests:
            cpu: 1000m
            memory: 8Gi
      volumeSize: 50Gi
      version: 8.13.4

Default Configuration

By default, CNE GCP Ready provisions a single-node Elasticsearch cluster with these settings:

Setting	Default
nodeCount	1
resources.requests.cpu	500m
resources.requests.memory	4Gi
resources.limits.cpu	1000m
resources.limits.memory	8Gi
volumeSize	8Gi
storageClassName	standard-rwo
Self-signed TLS	Disabled
Pre-installed plugins	analysis-icu, analysis-kuromoji, analysis-smartcn, analysis-stempel

Elasticsearch Version Compatibility

ECK operator versions support specific Elasticsearch versions.

Before upgrading Elasticsearch, verify compatibility between

• The ECK operator version
• The Elasticsearch version

For compatibility details, see ECK support matrix.

Liferay Integration

The base Liferay Helm chart includes the Elasticsearch connection configuration by default.

You do not need additional liferay.yaml overrides to connect Liferay to the in-cluster Elasticsearch deployment.

Limitations

GCP environments do not provision a managed OpenSearch or Elasticsearch service.

Elasticsearch deployed through ECK is the supported search platform for CNE GCP Ready environments.