Skip to main content

​
Coverage Matrix

​
Elasticsearch (ECK) Operator Overview

Elasticsearch (ECK) Operator is Elastic’s official operator for managing Elasticsearch, Kibana, and other Elastic Stack components. It automates stateful operations using custom resource definitions (CRDs), ensuring consistent deployment, scaling, and upgrades. Platform engineers benefit from built-in best practices, such as automatic TLS certificate management, RBAC setup, and rolling upgrades. The operator proactively monitors cluster health, managing tasks like node replacement or shard reallocation without manual intervention. By simplifying the Elastic lifecycle, ECK reduces operational overhead while ensuring reliability and consistency in large environments.

​
Chkk Coverage

​
Curated Release Notes

Chkk provides curated summaries of ECK release notes, highlighting critical operational impacts like compatibility changes, new features, or deprecated configurations. If ECK removes support for older Elasticsearch versions or introduces mandatory configuration changes, Chkk clearly flags these details. Engineers receive targeted notifications—such as required Kubernetes version upgrades or new CRDs—allowing proactive maintenance. This streamlined insight prevents platform engineers from manually parsing lengthy upstream release logs, focusing instead on actionable information.

​
Preflight & Postflight Checks

Chkk performs preflight checks prior to upgrades, validating Elastic versions, CRD compatibility, and deprecated configurations. It warns of unsupported multi-version jumps and identifies potential resource conflicts. Post-upgrade, Chkk verifies operator health, checks Elasticsearch cluster statuses, and detects stalled pod restarts. Automated issue detection like webhook validation errors or resource constraints helps engineers address upgrade anomalies swiftly, minimizing downtime.

​
Version Recommendations

Chkk monitors ECK’s support lifecycle, proactively alerting engineers as their installed version nears end-of-life or loses security patch support. It references Elastic’s official support matrix and compatibility guidelines, suggesting stable upgrade paths that balance new features and operational reliability. For example, Chkk warns if your current ECK version lacks support for an upcoming cluster release. Custom support timelines for vendor-specific or forked ECK versions are also respected, ensuring alignment with internal policies.

​
Upgrade Templates

Chkk supplies detailed templates for both in-place and blue-green upgrades, embedding Elastic’s recommended best practices. In-place upgrades outline necessary steps like CRD updates, operator deployment changes, and post-upgrade validations. Blue-green upgrades detail dual-operator deployments, namespace isolation strategies, and incremental migration plans for cautious rollouts. Templates explicitly include rollback points and compatibility checks, reducing human error during complex upgrades.

​
Preverification

Chkk’s preverification simulates ECK upgrades within a safe staging environment, surfacing conflicts or errors without impacting production. By recreating representative Elastic resources, Chkk identifies potential issues such as CRD mismatches, pod scheduling failures, or RBAC conflicts. Issues encountered during simulation—like resource overconsumption or webhook connectivity failures—are clearly reported. This proactive testing significantly reduces unknown risks in live upgrade scenarios.

​
Supported Packages

Chkk seamlessly integrates with various ECK deployment methods, including Helm charts, OperatorHub/OLM, or plain manifests. It adapts upgrade instructions based on your existing deployment, preserving custom configurations and image registries. Whether using cluster-wide or namespace-scoped operators, Chkk provides precise upgrade guidance without disrupting existing workflows. Integration into GitOps or CI/CD pipelines ensures engineers apply upgrade recommendations consistently and efficiently.

​
Additional Resources