Files
Kubernetes-Manifests/infra/crowdsec/values.yaml
T
Jeffrey dcb127e9e8 crowdsec: add LAPI + AppSec and the Envoy ext_authz bouncer
Detection is CAPI community blocklists plus AppSec inline WAF, not Envoy
access-log parsing. Enforcement is gRPC ext_authz from Envoy Gateway.

Changes from the draft that was held:

Agent disabled rather than given an empty acquisition list. Chart 0.24.0
refuses to render the DaemonSet with acquisition: [] ("No acquisition or
additionalAcquisition configured"), and with no log tailing the agent has
nothing to do. The WAF collections moved to appsec.env, where they belong,
and base-http-scenarios was dropped since it only feeds log parsing. AppSec
registers with LAPI on its own, so it works without the agent.

Bouncer values updated for chart 0.8.0 (the app already pinned 0.8.0 while the
values were written against 0.6.3). Added waf.failOpen: true, whose chart
default is false and would deny every request if AppSec were unreachable.

SecurityPolicy now targets the whole gateway-public rather than the it-tools
listener. EG v1.3.2 rejects targetRefs.sectionName on SecurityPolicy, and
targeting the HTTPRoute instead would gate LAN traffic too since public routes
also parent gateway-internal. Blanket coverage of the public gateway is what we
want anyway, and failOpen keeps a bouncer outage from taking public apps down.

envoyproxy-public.yaml is kept as documentation but not applied. EG v1.3.2
already defaults envoyService.externalTrafficPolicy to Local, verified live on
all three gateway LB services, so the real client IP already reaches Envoy.

Not wired into the envoy-gateway kustomization yet. That lands once the
bouncer is up and healthy.
2026-08-26 17:00:34 +02:00

58 lines
2.0 KiB
YAML

# CrowdSec core — chart crowdsecurity/crowdsec 0.24.0 (appVersion v1.7.8)
# Deploys: LAPI (decisions DB), log-processing agent, and AppSec (WAF) component.
#
# Detection strategy here = CAPI community blocklists + AppSec (inline WAF).
# We intentionally do NOT parse Envoy access logs (no reliable first-party
# Envoy parser); the kdwils bouncer forwards requests to AppSec instead.
# Remediation/enforcement is done by the separate `crowdsec-envoy-bouncer`.
#=============================#
#= Local API (LAPI) =#
#=============================#
lapi:
# Pre-register the "envoy" bouncer. The CrowdSec image turns BOUNCER_KEY_<name>
# into a registered bouncer named <name> on first start. The kdwils bouncer
# authenticates with this same key.
env:
- name: BOUNCER_KEY_envoy
valueFrom:
secretKeyRef:
name: crowdsec-secrets
key: bouncer-key
persistentVolume:
data:
enabled: true
storageClassName: longhorn
size: 2Gi
config:
enabled: true
storageClassName: longhorn
size: 100Mi
#=============================#
#= Log-processing agent =#
#=============================#
agent:
# Disabled: detection comes from AppSec + CAPI, not log tailing. Chart 0.24.0
# refuses to render the agent DaemonSet with an empty acquisition list anyway.
enabled: false
#=============================#
#= AppSec (WAF) component =#
#=============================#
appsec:
enabled: true
# Hub collections installed into the AppSec pod at startup (the WAF rule sets).
env:
- name: COLLECTIONS
value: "crowdsecurity/appsec-virtual-patching crowdsecurity/appsec-generic-rules"
acquisitions:
- source: appsec
listen_addr: "0.0.0.0:7422"
path: /
# Virtual-patching ruleset (CRS-based vpatch rules). Verify it loaded after
# first deploy with: cscli appsec-configs list / cscli appsec-rules list
appsec_config: crowdsecurity/virtual-patching
labels:
type: appsec