rancher-partner-charts/charts/crowdstrike/falcon-sensor/values.yaml

255 lines
8.0 KiB
YAML
Raw Normal View History

# Default values for falcon-sensor.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
node:
# When enabled, Helm chart deploys the Falcon Sensors to Kubernetes nodes
enabled: true
# Overrides the backend leveraged by the Falcon Sensor (kernel, bpf)
backend: kernel
# Enable for use on Google's GKE Autopilot clusters
gke:
autopilot: false
daemonset:
# Annotations to apply to the daemonset
annotations: {}
# The key that is used to handle enabling/disabling sensor injection at the pod/node level
podAnnotationKey: sensor.falcon-system.crowdstrike.com/injection
# additionals labels
labels: {}
# Enable the priorityClass creation on chart installation
priorityClassCreate: true
# Assign a PriorityClassName to pods if set
priorityClassName: ""
priorityClassValue: 1000000000
tolerations:
# We want to schedule on control plane nodes where they are accessible
- key: "node-role.kubernetes.io/master"
operator: "Exists"
effect: "NoSchedule"
# Future taint for K8s >=1.24
- key: "node-role.kubernetes.io/control-plane"
operator: "Exists"
effect: "NoSchedule"
- key: "kubernetes.azure.com/scalesetpriority"
operator: "Equal"
value: "spot"
effect: "NoSchedule"
# Daemonsets automatically get additional tolerations: https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/
# https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
# Allow setting additional node selections e.g. processor type
# nodeAffinity:
# requiredDuringSchedulingIgnoredDuringExecution:
# nodeSelectorTerms:
# - matchExpressions:
# - key: kubernetes.io/arch
# operator: In
# values:
# - amd64
nodeAffinity: {}
# Resource settings that can be set with backend is set to bpf only. Cannot be used when backend is set to kernel.
# This will be ignored if backend is set to kernel. Purposefully. The defaults are set to the minimum requirements.
# Depending on the size of your cluster and the node types, you may need to increase these values.
# resources:
# limits:
# cpu: 250m
# ephemeral-storage: 100Mi
# memory: 500Mi
# requests:
# cpu: 250m
# ephemeral-storage: 100Mi
# memory: 500Mi
# Update strategy to role out new daemonset configuration to the nodes.
updateStrategy: RollingUpdate
# Sets the max unavailable nodes. Default is 1 when no value exists.
maxUnavailable: 1
image:
repository: falcon-node-sensor
pullPolicy: Always
pullSecrets:
# Overrides the image tag. In general, tags should not be used (including semver tags or `latest`). This variable is provided for those
# who have yet to move off of using tags. The sha256 digest should be used in place of tags for increased security and image immutability.
tag: "latest"
# Setting a digest will override any tag and should be used instead of tags.
#
# Example digest variable configuration:
# digest: sha256:ffdc91f66ef8570bd7612cf19145563a787f552656f5eec43cd80ef9caca0398
digest:
# Value must be base64. This setting conflicts with node.image.pullSecrets
# The base64 encoded string of the docker config json for the pull secret can be
# gotten through:
# $ cat ~/.docker/config.json | base64 -
registryConfigJSON:
podAnnotations: {}
# How long to wait for Falcon pods to stop gracefully
terminationGracePeriod: 30
container:
# When enabled, Helm chart deploys the Falcon Container Sensor to Pods through Webhooks
enabled: false
# Configure the number of replicas for the mutating webhook backend
replicas: 2
# Configure PodTopologySpread constraints to allow pods run on different nodes
topologySpreadConstraints:
- maxSkew: 1
topologyKey: kubernetes.io/hostname
whenUnsatisfiable: ScheduleAnyway
labelSelector:
matchLabels:
crowdstrike.com/component: crowdstrike-falcon-injector
# Auto update the certificates every time there is an update
autoCertificateUpdate: true
# Update Webhook and roll out new Deployment on upgrade
autoDeploymentUpdate: true
# For AKS without the pulltoken option
azure:
enabled: false
# Path to the Kubernetes Azure config file on worker nodes
azureConfig: /etc/kubernetes/azure.json
# GCP GKE workload identity init container
gcp:
enabled: false
# Enable Network Policies within the Injector namespace to allow ingress
networkPolicy:
enabled: false
Charts CI ``` Updated: argo/argo-cd: - 5.52.1 bitnami/airflow: - 16.1.11 bitnami/cassandra: - 10.6.9 bitnami/kafka: - 26.6.3 bitnami/mariadb: - 15.0.1 bitnami/mysql: - 9.16.1 bitnami/postgresql: - 13.2.29 bitnami/redis: - 18.6.3 bitnami/spark: - 8.1.8 bitnami/tomcat: - 10.11.11 bitnami/wordpress: - 19.0.5 bitnami/zookeeper: - 12.4.4 cert-manager/cert-manager: - v1.13.3 clastix/kamaji: - 0.14.0 cockroach-labs/cockroachdb: - 11.2.3 confluent/confluent-for-kubernetes: - 0.824.40 crowdstrike/falcon-sensor: - 1.24.1 datadog/datadog: - 3.50.5 datadog/datadog-operator: - 1.4.1 dell/csi-isilon: - 2.9.0 dell/csi-powermax: - 2.9.0 dell/csi-powerstore: - 2.9.0 dell/csi-unity: - 2.9.0 dell/csi-vxflexos: - 2.9.0 digitalis/vals-operator: - 0.7.8 dynatrace/dynatrace-operator: - 0.15.0 external-secrets/external-secrets: - 0.9.11 f5/nginx-ingress: - 1.1.0 fairwinds/polaris: - 5.17.0 gluu/gluu: - 5.0.24 haproxy/haproxy: - 1.35.5 harbor/harbor: - 1.14.0 hashicorp/consul: - 1.3.1 instana/instana-agent: - 1.2.66 intel/intel-device-plugins-operator: - 0.29.0 intel/intel-device-plugins-qat: - 0.29.0 intel/intel-device-plugins-sgx: - 0.29.0 jenkins/jenkins: - 4.11.2 jfrog/artifactory-ha: - 107.71.11 jfrog/artifactory-jcr: - 107.71.11 kong/kong: - 2.33.3 kubecost/cost-analyzer: - 1.108.1 kuma/kuma: - 2.5.1 linkerd/linkerd-control-plane: - 1.16.9 mongodb/community-operator: - 0.9.0 nats/nats: - 1.1.6 new-relic/nri-bundle: - 5.0.58 nutanix/nutanix-csi-snapshot: - 6.3.2 nutanix/nutanix-csi-storage: - 2.6.6 openebs/openebs: - 3.10.0 percona/psmdb-db: - 1.15.1 percona/pxc-db: - 1.13.4 redpanda/redpanda: - 5.7.7 speedscale/speedscale-operator: - 2.0.2 stackstate/stackstate-k8s-agent: - 1.0.66 sysdig/sysdig: - 1.16.24 traefik/traefik: - 26.0.0 trilio/k8s-triliovault-operator: - 4.0.0 weka/csi-wekafsplugin: - 2.3.2 yugabyte/yugabyte: - 2.18.5 yugabyte/yugaware: - 2.18.5 ```
2024-01-12 17:13:39 +00:00
# Enable using hostNetwork for the injector pod
hostNetwork: false
# Disable injection for all Namespaces
disableNSInjection: false
# Disable injection for all Pods
disablePodInjection: false
# Certificate validity duration in number of days
certExpiration: 3650
# Configure the Injector Port
injectorPort: 4433
# Configure the requests and limits of the sensor
sensorResources:
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 10m
# memory: 20Mi
# For custom DNS configurations when .svc requires a domain for services
# For example if service.my-namespace.svc doesn't resolve and the cluster uses
# service.my-namespace.svc.testing.io, you would add testing.io as the value below.
# Otherwise, keep this blank.
domainName:
# Provide a Secret containing CA certificate files.
# All CA certificates need to be a valid secret key, and have the extension ".crt"
# Example: kubectl create secret generic external-registry-cas --from-file=/tmp/thawte-Primary-Root-CA.crt --from-file=/tmp/DigiCert-Global-Root-CA.crt
#
# registryCertSecret: external-registry-cas
registryCertSecret:
# The key that is used to handle enabling/disabling sensor injection at the namespace level
namespaceLabelKey: sensor.falcon-system.crowdstrike.com/injection
image:
repository: falcon-sensor
pullPolicy: Always
# Set to true if connecting to a registry that requires authentication
pullSecrets:
enable: false
name:
# Configure the list of namespaces that should have access to pull the Falcon
# sensor from a registry that requires authentication. This is a comma separated
# list. For example:
#
# namespaces: ns1,ns2,ns3
namespaces:
# Attempt to create the Falcon sensor pull secret in all Namespaces
# instead of using "container.image.pullSecrets.namespaces"
allNamespaces: false
# Value must be base64
# The base64 encoded string of the docker config json for the pull secret can be
# gotten through:
# $ cat ~/.docker/config.json | base64 -
registryConfigJSON:
# Overrides the image tag. In general, tags should not be used (including semver tags or `latest`). This variable is provided for those
# who have yet to move off of using tags. The sha256 digest should be used in place of tags for increased security and image immutability.
tag: "latest"
# Setting a digest will override any tag and should be used instead of tags.
#
# Example digest variable configuration:
# digest: sha256:ffdc91f66ef8570bd7612cf19145563a787f552656f5eec43cd80ef9caca0398
digest:
# Annotations to apply to the injector deployment
annotations: {}
# additionals labels to apply to the injector deployment
labels: {}
# Annotations to apply to the injector deployment
podAnnotations: {}
tolerations: []
resources:
# limits:
# cpu: 100m
# memory: 128Mi
requests:
cpu: 10m
memory: 20Mi
serviceAccount:
name: crowdstrike-falcon-sa
annotations: {}
# Deploys the test suite during install for testing purposes.
testing:
enabled: false
falcon:
cid:
apd:
aph:
app:
trace: none
feature:
message_log:
billing:
tags:
provisioning_token:
# Override various naming aspects of this chart
# Only edit these if you know what you're doing
nameOverride: ""
fullnameOverride: ""