Coralogix Operator

Warning

Security advisory (Priority: Medium): On October 20, 2026, the private keys for 8 intermediate certificate authorities operated by eMudhra were reported compromised. This is an industry-wide issue, not specific to Coralogix. Update the Coralogix Operator to v2.16.0 (FIPS build: v2.16.0-fips) or later out of an abundance of caution. Coralogix endpoints and internal services do not use eMudhra or emSign certificates, and we have not identified any impact to customer data.

See the eMudhra security advisory for full upgrade guidance and breaking-change details.

If you have any questions or need help upgrading, our Support team is here to help. Reach out through in-app chat and mention "Security advisory eMudhra" and the required component.

Overview

Changed in v2.3.1

The Coralogix Operator provides Kubernetes-native deployment and management for Coralogix, designed to simplify and automate the configuration of Coralogix APIs through Kubernetes Custom Resource Definitions (CRDs) and controllers.

The operator provides the following capabilities:

• CRDs and controllers: Easily deploy and manage various Coralogix features using custom resources, which are automatically reconciled by the operator. For a complete list of available CRDs and their details, refer to the API documentation. For examples of custom resources, refer to the samples directory.
• Prometheus Operator integration: The Operator uses PrometheusRule CRD, to simplify the transition to Coralogix Alerts by utilizing existing monitoring configurations. For more details on this integration, refer to the Prometheus Integration documentation.
• Metrics collection: The operator provides metrics for monitoring custom resources and the operator itself. For more details, refer to the Metrics documentation.

FIPS image

Other than the default Coralogix Operator image, each release is also published as an image built with a Federal Information Processing Standards (FIPS) 140 validated cryptographic module, for use in FedRAMP or similar environments.

The FIPS image is built with the Go Cryptographic Module v1.0.0, covered by NIST Cryptographic Module Validation Program (CMVP) certificate #5247, and is published from v2.14.0 onwards as coralogixrepo/coralogix-operator:vX.Y.Z-fips and latest-fips.

Prerequisites

• Kubernetes cluster (v1.16+)
• Prometheus Operator. By default, the PrometheusRule Integration is enabled, and a ServiceMonitor is created for the operator. These CRDs are part of the Prometheus Operator. If you are not using Prometheus Operator, you can disable it by setting the coralogixOperator.prometheusRules.enabled=false and serviceMonitor.create=false flags during installation.

Installation

To install, upgrade, or uninstall the Coralogix Operator, using either the standard or the FIPS image:

1. Add the Coralogix Helm repository and update it:

   helm repo add coralogix https://cgx.jfrog.io/artifactory/coralogix-charts-virtual
   helm repo update

2. Install the Coralogix Operator:

   helm install <my-release> coralogix/coralogix-operator \
     --set secret.data.apiKey="<api-key>" \
     --set coralogixOperator.region="<region>"

   Or, to install the operator using the FIPS image:

   helm install <my-release> coralogix/coralogix-operator \
     --set secret.data.apiKey="<api-key>" \
     --set coralogixOperator.image.fips=true \
     --set coralogixOperator.region="<region>"

   Omit coralogixOperator.image.tag. The image tag then follows the chart appVersion through every upgrade, and the chart appends -fips to it when coralogixOperator.image.fips=true.

   For a complete list of configuration options, refer to the Helm Chart Docs.

3. To upgrade the operator:

   helm upgrade <my-release> coralogix/coralogix-operator \
     --set secret.data.apiKey="<api-key>" \
     --set coralogixOperator.region="<region>"

   Or, to update the operator using the FIPS image:

   helm upgrade <my-release> coralogix/coralogix-operator \
     --set secret.data.apiKey="<api-key>" \
     --set coralogixOperator.image.fips=true \
     --set coralogixOperator.region="<region>"

   A value you omit from helm upgrade --set returns to the chart default, so an upgrade that leaves out --set coralogixOperator.image.fips=true moves the release back to the standard image without reporting an error. Repeat the flag on every upgrade of a FIPS release.

   To check which image a release runs:

   kubectl get deployment -A -l app.kubernetes.io/instance=<my-release> \
     -o jsonpath='{.items[*].spec.template.spec.containers[0].image}'

4. To uninstall the operator, run:

   helm delete <my-release>

Optional: Operator Self Monitoring

To help you monitor the health and performance of the Coralogix Operator, we've included a set of recommended resources in this repository. These resources are optional, but recommended for observability, debugging, and operational visibility in production environments. To install, run:

kubectl apply -f https://raw.githubusercontent.com/coralogix/coralogix-operator/refs/heads/main/config/self_monitoring/alert_crs_not_synced.yaml
kubectl apply -f https://raw.githubusercontent.com/coralogix/coralogix-operator/refs/heads/main/config/self_monitoring/alert_reconcile_error_high.yaml
kubectl apply -f https://raw.githubusercontent.com/coralogix/coralogix-operator/refs/heads/main/config/self_monitoring/dashboard-json.yaml
kubectl apply -f https://raw.githubusercontent.com/coralogix/coralogix-operator/refs/heads/main/config/self_monitoring/dashboards_folder.yaml
kubectl apply -f https://raw.githubusercontent.com/coralogix/coralogix-operator/refs/heads/main/config/self_monitoring/recording_rule_group_sets.yaml

Contributing

Please refer to CONTRIBUTING.md.

How it works

This project aims to follow the Kubernetes Operator pattern. It uses Controllers which provides a reconcile function responsible for synchronizing resources until the Desired state is reached on the cluster.