Create a helm chart to install falcon-operator

[thatmlopsguy]

Please create an official falcon-operator helm chart to deploy via gitOps using ArgoCD or FluxCD.

Secret variables like falcon_cid should be imported via a secretRef.

Thanks.

[YvesEarnix]

@thatmlopsguy I agree that an helm chart will be welcome

About secret variables it's already supported by the operator.

kind: FalconNodeSensor
metadata:
  name: falcon-node-sensor
spec:
  falcon:
    trace: none
  falcon_api:
    cloud_region: autodiscover
  falconSecret:
    enabled: true
    secretName: falcon-secrets
    namespace: falcon-operator

---- the secret ---
Name:         falcon-secrets
Namespace:    falcon-operator
Type:  Opaque
Data
====
falcon-cid:         
falcon-client-id:     
falcon-client-secret:  

[falcon-pioupiou]

@thatmlopsguy @YvesEarnix question : a helm chart for falcon-operator because you are using OpenShift ? if not OpenShift, there is a direct helm chart : https://github.com/CrowdStrike/falcon-helm/tree/main

[thatmlopsguy]

@falcon-pioupiou there is no falcon-operator helm chart.

[falcon-pioupiou]

@thatmlopsguy I know - I'm looking for the usage - operator is needed on OpenShift while on other type of k8s (with argocd or flux) - Falcon agents' helm chart can be used - that's why this question and also to highlight the fact that helm charts exists for direct deployment.

[thatmlopsguy]

Our idea is to deploy the falcon-operator to k8s (not OpenShift) with argocd, using an applicationset with two sources: the first one is to deploy falcon-operator helm chart and the second source it will be an internal helm chart with the CR from falcon-operator. From a platform engineer perspective makes more sense, instead of deploy several helm charts (sensor, image-analyzer, kac)from the repo you mention.