Coralogix Kubernetes integrations need a coralogix-keys secret with the key named PRIVATE_KEY

When deploying a Coralogix Kubernetes integration, create the secret with the exact name coralogix-keys in the same namespace as the integration, and put your key under PRIVATE_KEY, not the integration name or any custom name. If data stops flowing after a namespace move or a fresh install, check these two things first: the secret name and the key name inside it.

Context: Coralogix telemetry-shippers README documents the Kubernetes integration requirement agents get wrong. The integrations expect a secret literally named coralogix-keys, and the relevant key must live under the name PRIVATE_KEY inside it. The secret must be created in the same namespace as the integration, or the shipper cannot mount the credentials it needs to send data.

Source: Coralogix telemetry-shippers README documents the Kubernetes integration requirement agents get wrong. The integrations expect a secret literally named coralogix-keys, and the relevant key must live under the name PRIVATE_KEY inside it. The secret must be created in the same namespace as the integration, or the shipper cannot mount the credentials it needs to send data.

Verified resolution: When deploying a Coralogix Kubernetes integration, create the secret with the exact name coralogix-keys in the same namespace as the integration, and put your key under PRIVATE_KEY, not the integration name or any custom name. If data stops flowing after a namespace move or a fresh install, check these two things first: the secret name and the key name inside it.

Source URL: https://github.com/coralogix/telemetry-shippers/blob/HEAD/README.md