Skip to main content
Deprecated — v1.x chartThis page documents cloud deployments for the v1.x inline-template Helm chart, which is in maintenance mode. For the v2.x chart, see Helm cloud deployments. To migrate, see the Upgrade guide.
This guide covers cloud-specific configurations for deploying ClickStack on managed Kubernetes services. For basic installation, see the main Helm deployment guide.

Google Kubernetes Engine (GKE)

When deploying to GKE, you may need to override certain values due to cloud-specific networking behavior.

LoadBalancer DNS resolution issue

GKE’s LoadBalancer service can cause internal DNS resolution issues where pod-to-pod communication resolves to external IPs instead of staying within the cluster network. This specifically affects the OTEL collector’s connection to the OpAMP server. Symptoms:
  • OTEL collector logs showing “connection refused” errors with cluster IP addresses
  • OpAMP connection failures like: dial tcp 34.118.227.30:4320: connect: connection refused
Solution: Use the fully qualified domain name (FQDN) for the OpAMP server URL:

Other GKE considerations

Amazon EKS

For EKS deployments, consider these common configurations:

Azure AKS

For AKS deployments:

Production Cloud deployment checklist

Before deploying ClickStack to production on any cloud provider:
  • Configure proper frontendUrl with your external domain/IP
  • Set up ingress with TLS for HTTPS access
  • Override otel.opampServerUrl with FQDN if experiencing connection issues (especially on GKE)
  • Adjust clickhouse.config.clusterCidrs for your pod network CIDR
  • Configure persistent storage for production workloads
  • Set appropriate resource requests and limits
  • Enable monitoring and alerting
  • Configure backup and disaster recovery
  • Implement proper secret management

Production best practices

Resource management

High availability

Persistent storage

Ensure persistent volumes are configured for data retention:
Cloud-specific storage classes:
  • GKE: pd-ssd or pd-balanced
  • EKS: gp3 or io2
  • AKS: managed-premium or managed-csi

Browser compatibility notes

For HTTP-only deployments (development/testing), some browsers may show crypto API errors due to secure context requirements. For production deployments, always use HTTPS with proper TLS certificates through ingress configuration. See Ingress configuration for TLS setup instructions.

Next steps

Last modified on July 2, 2026