Files
kubernetes/clusters/production/webhook-receiver.yaml
Suriya c526d494b0 Fix Receiver type: gitea is not a valid Flux receiver type
The installed Flux version's Receiver CRD rejects type: gitea, which
failed dry-run validation and blocked the entire flux-system
Kustomization batch from applying - including the alaska/core stacks.
Switched to type: generic (no payload parsing needed for a trigger-only
webhook).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-20 10:33:10 +05:30

21 lines
809 B
YAML

# The referenced Secret (gitea-webhook-token) is created directly on the
# cluster, not committed here - see the server-side command sequence.
apiVersion: notification.toolkit.fluxcd.io/v1
kind: Receiver
metadata:
name: gitea-receiver
namespace: flux-system
spec:
# This Flux version's Receiver CRD has no "gitea" type - valid values are
# generic, generic-hmac, generic-oidc, github, gitlab, bitbucket, harbor,
# dockerhub, quay, gcr, nexus, acr, cdevents. "generic" accepts any POST
# to the hook path without payload/signature parsing, which is fine here:
# worst case is an early sync trigger, not a permission escalation.
type: generic
secretRef:
name: gitea-webhook-token
resources:
- apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
name: flux-system