Skip to main content

FluxCD Installation

This installation method enables Causely on Kubernetes clusters using FluxCD for GitOps-based deployment and management.

Prerequisites​

  • Kubernetes cluster running
  • FluxCD installed and configured
  • Git repository for storing configuration
  • Linux kernel with eBPF support (5.4+ recommended)

1. Install Causely using FluxCD​

Step 1: Retrieve Your Access Token​

  1. Visit https://portal.causely.app and log in.
  2. Click on the gear icon in the top-right corner and select Integrations
  3. Click the Details 🗝️ button and copy your access token to use in the next step.

Step 2: Get the FluxCD manifests​

Download the FluxCD manifests and copy them to your GitOps repository:

# Clone the causely-deploy repository to get the manifests
git clone https://github.com/causely-oss/causely-deploy.git
cd causely-deploy/kubernetes/fluxcd/causely

# Copy the manifests to your GitOps repository
cp *.yaml /path/to/your/gitops-repo/causely/

Alternatively, you can copy the files directly from the causely-deploy repository into your GitOps repository.

Step 3: Configure your environment​

Create the Kubernetes Secret for your token​

First, create a Kubernetes secret containing your gateway token:

kubectl create secret generic causely-secrets \
  --from-literal=CAUSELY_TOKEN=your-actual-gateway-token-here \
  -n causely

Update the configuration files​

Edit the configuration files to match your environment. The version and token are now managed through Flux CD's native variable substitution:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
  - namespace.yaml
  - release.yaml
  - repository.yaml

# Flux CD native variable substitution
postBuild:
  substitute:
    CAUSELY_VERSION: 'v1.0.92-0-g032e39faaf05c408'
  substituteFrom:
    - kind: Secret
      name: causely-secrets
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: causely
  namespace: causely
spec:
  interval: 1h
  chart:
    spec:
      chart: causely
      version: ${CAUSELY_VERSION}
      sourceRef:
        kind: HelmRepository
        name: causely
        namespace: causely
  values:
    global:
      cluster_name: production # Update to your cluster name

    image:
      tag: ${CAUSELY_VERSION}

    mediator:
      gateway:
        token: ${CAUSELY_TOKEN}

Update the version (optional)​

To update the Causely version, edit the CAUSELY_VERSION value in kustomization.yaml:

postBuild:
  substitute:
    CAUSELY_VERSION: '<version>' # Update to your desired version

Step 4: Deploy via GitOps​

Navigate to your GitOps repository and commit the changes:

# Navigate to your GitOps repository
cd /path/to/your/gitops-repo

# Add the Causely configuration files
git add causely/
git commit -m "Add Causely FluxCD configuration"
git push origin main

FluxCD will automatically detect the changes and deploy Causely to your cluster. You can monitor the deployment status:

# Check FluxCD reconciliation status
kubectl get helmreleases -n causely

# Check if Causely pods are running
kubectl get pods -n causely

Step 5: Review Discovery​

To verify the agent is successfully installed navigate to the Integrations Agents view. Once the agent has appeared you have successfully installed Causely!

Navigate to https://portal.causely.app to verify your environment has been discovered. You should see entities populated in the Topology view. As root causes are identified, they will appear in the Root Cause view.

Next Steps​

Visit the Customize your Installation page to learn more about customizing your installation.

We recommend that you connect additional telemetry sources to help Causely identify root causes in your environment. Visit the Telemetry Sources page to learn more about the data sources that Causely supports.

To push insights into your workflows, visit the Workflow Integrations page.