Hello everyone, Our current Production Elasticsearch cluster for logs collection is manually managed and runs on AWS. I'm creating the same cluster using ECK deployed with Helm under Terraform. I was able to get all the features replicated (S3 repo for snapshots, ingest pipelines, index templates…

In the end the problem was that the eck operator does a lot of changes in the spec session, so if you add the whole "spec" to the computed_fields those changes are ignored and the upgrade proceed as intended: resource "kubernetes_manifest" "elasticsearch_deploy" { field_manager { force_confli…

Discuss the Elastic Stack

Upgrade ES version managed by ECK on terraform - all pods terminated

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)

Roberto_D_Arco (Roberto D'Arco) December 13, 2022, 10:07am 2

I think I'm having the same problem as in Deploy Elasticsearch Custom Resource with Terraform

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.