I have a Kubernetes cluster A where I deployed an Elasticsearch cluster A with the Operator. Now, I have a Kubernetes cluster B where I want to deploy an Elasticsearch cluster B but I would like for it to be managed by the same ECK instance as Elasticsearch cluster A. Is there any way to achieve this ?
This isn’t supported from an architectural standpoint.
ECK is a Kubernetes operator and is tightly coupled to the Kubernetes API server of the cluster where it runs. It watches and reconciles Elasticsearch custom resources (CRDs) locally, so a single ECK instance cannot manage deployments across multiple Kubernetes clusters.
If you are running Elasticsearch in multiple Kubernetes clusters, the recommended and supported approach is to deploy one ECK operator per Kubernetes cluster.
If your goal is centralized operations or data access across clusters, you should look at:
• Cross-Cluster Search (CCS) for federated querying
• Cross-Cluster Replication (CCR) for data replication
• Or a hub-and-spoke architecture with a central monitoring cluster
Operational control, however, remains scoped to each Kubernetes cluster by design.