Skip to main content

Coralogix Operator

The Coralogix Operator gives you a Kubernetes-native way to manage Coralogix observability resources. Define alerts, recording rules, parsing rules, dashboards, and other Coralogix entities as Kubernetes Custom Resources, then let the operator reconcile them with the Coralogix platform. This enables GitOps workflows, configuration as code, and consistent management across multiple clusters and environments.

What it does

The operator watches Custom Resource Definitions (CRDs) in your cluster and translates them into API calls against Coralogix. Changes made through kubectl apply propagate to Coralogix automatically; resources removed from the cluster are cleaned up on the platform side.

Supported resource types include alerts, recording rules, parsing rules, and dashboards. The exact list depends on the operator version installed.

When to use it

  • You manage Kubernetes infrastructure with GitOps tooling such as Argo CD or Flux and want Coralogix configuration to follow the same workflow.
  • You operate multiple Kubernetes clusters and need consistent Coralogix configuration applied across them.
  • Your team prefers declarative Kubernetes manifests over UI configuration or direct API calls.
  • You want pull-request review and version control for Coralogix configuration changes.

Installation

The operator is distributed as a Helm chart and installed alongside the Coralogix Kubernetes integration. See Kubernetes complete observability basic configuration for the full setup including the operator prerequisites.

Generate Custom Resource manifests

The MCP server can generate Kubernetes manifests for Coralogix resources you already have configured. See:

Support

Reach the Coralogix customer success team 24/7 via in-app chat or by email at support@coralogix.com.

Next steps

Learn about complementary infrastructure-as-code options in the Coralogix Terraform Provider.

Was this page helpful?