1a6f537a46f4e9818b620bdcf7cf3c1b2ed4cb93
ci/woodpecker/cron/security-scan Pipeline was successful
Move CrowdSec to infrastructure stage with a Job that: 1. Waits for CrowdSec LAPI to be ready 2. Generates a bouncer API key via cscli 3. Creates a K8s Secret in the ingress namespace ingress-nginx HelmRelease depends on CrowdSec, uses the CrowdSec controller image, and reads the bouncer key from the provisioned secret. No SealedSecrets or hardcoded keys needed. Flow: CrowdSec deploys → Job creates bouncer key → ingress-nginx starts with bouncer plugin authenticated to LAPI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Description
No description provided
38 MiB