Alek's Blog - ovh

Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse: Kubernetes Operations, Backup & DR

aleks — Thu, 14 May 2026 00:00:00 +0000

Cluster setup, ingest pipelines, and backup & disaster recovery differ significantly across Elasticsearch, OpenSearch, Grafana Loki, Quickwit, and ClickHouse — and these differences often matter more than raw performance when a log archive must run reliably for 7+ years.

This is Part 2 of a five-part series.

Full guide: Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse: The Complete Guide</a></li>
Part 1 — Comparison:</a> Storage tiering, compression, resource consumption, query languages, SaaS options</li>
Part 2 — Operations — this post: Setup, ingest pipeline, ECS vs. OTel, backup & DR, observability, alerting</li>
Part 3 — Security & Compliance:</a> Encryption, RBAC, WORM / S3 Object Lock</li>
Part 4 — UX, Dashboards & Alerts:</a> UI layers, log search UX, cold-tier query behaviour, dashboard building, sharing, alerting</li>
Part 5 — Use Case:</a> Vector, Istio/Envoy, nginx, Java on OVH MKS — complete ClickHouse ingestion setup and monthly awffull report</li> </ul>

Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse: Long-Term Log Archiving for 7+ Years

aleks — Thu, 14 May 2026 00:00:00 +0000

Long-term log archiving is a deep topic. Each of the five systems covered here has its own tiering model, object storage integration, query language, operational quirks, and security posture. To do it justice, this comparison is split across five posts — take your time reading them, and don’t hesitate to come back to individual sections more than once.
Full guide: Elasticsearch vs. OpenSearch vs. Loki vs. Quickwit vs. ClickHouse: The Complete Guide</a></li>
Part 1 — this post: Storage tiering, compression, resource consumption, query languages, SaaS options</li>
Part 2 — Operations:</a> Setup, ingest pipeline, ECS vs. OTel, backup & DR, observability, alerting</li>
Part 3 — Security & Compliance:</a> Encryption, RBAC, WORM / S3 Object Lock</li>
Part 4 — UX, Dashboards & Alerts:</a> UI layers, log search UX, cold-tier query behaviour, dashboard building, sharing, alerting</li>
Part 5 — Use Case:</a> Vector, Istio/Envoy, nginx, Java on OVH MKS — complete ClickHouse ingestion setup and monthly awffull report</li> </ul>

Storing logs for compliance, auditing, or forensic purposes often means retaining data for seven years or more. That is a very different problem than storing the last 30 days of operational logs. Hot-tier query latency matters less; cost per GB, the ability to still search old data without restoring it manually, and the operational burden of keeping the system alive for years become the dominant concerns.
This post compares five systems — Elasticsearch</a>, OpenSearch</a>, Grafana Loki</a>, Quickwit</a>, and ClickHouse</a> — along the axes that matter for long-term archiving: tiering, object storage integration, compression, resource consumption during ingest/compact/search, and available SaaS options. A separate section covers systems that were evaluated but are not recommended for this use case.

Istio vs. Envoy Gateway: Gateway API on Kubernetes

aleks — Thu, 30 Apr 2026 00:00:00 +0000

Both Istio</a> and Envoy Gateway</a> implement the Kubernetes Gateway API</a> and use Envoy as their data plane. That is roughly where the similarity ends. Istio is a full service mesh that happens to implement Gateway API; Envoy Gateway is a dedicated Gateway API controller with no mesh ambitions. Choosing between them is mostly a question of scope.
This post starts with that comparison — architecture, mTLS, egress control, and resource overhead — then broadens to cover Cilium</a> as a lighter alternative for East-West security, how the choice plays out on managed Kubernetes offerings (AKS, GKE, and OVH MKS including their cloud-native ingress and egress options), and finally how to get the real client IP through a cloud load balancer to your application.