Flux Notification Receiver Quick Fix - Webhook Receiver Config

Flux Receiver resource accepts incoming webhooks from external systems (GitHub, GitLab, Bitbucket) to trigger reconciliations. Misconfigured receivers reject or ignore webhook payloads. This guide covers the fix.

Quick Fix

Wrong

apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Receiver
metadata:
  name: github-receiver
spec:
  type: github
  events:
  - ping
  - push

The issue: missing secretRef for webhook payload validation. Any sender can trigger reconciliations. Also missing resources to specify which resources to reconcile on webhook.

Right

apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Receiver
metadata:
  name: github-receiver
spec:
  type: github
  events:
  - ping
  - push
  secretRef:
    name: webhook-secret
  resources:
  - kind: GitRepository
    name: flux-system

# Expected output after applying the fix
# Receiver ready for GitHub webhooks
# Payload validated with webhook secret
# On push event: GitRepository flux-system reconciled
# Receiver status: True

Prevention

• Always configure secretRef for webhook payload authentication
• Specify resources to define which Flux resources reconcile on webhook
• Match type to the webhook source (github, gitlab, bitbucket, generic)
• List needed events for selective reconciliation triggering
• Verify receiver endpoint with kubectl describe receiver

DodaTech Tools

Doda Browser's receiver manager shows webhook delivery history and status. DodaZIP archives receiver configurations for audit. Durga Antivirus Pro validates webhook payloads.

FAQ