From c526d494b03022c6c015028ea02b722b0470f7b2 Mon Sep 17 00:00:00 2001 From: Suriya Date: Mon, 20 Jul 2026 10:33:01 +0530 Subject: [PATCH] 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 --- clusters/production/webhook-receiver.yaml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/clusters/production/webhook-receiver.yaml b/clusters/production/webhook-receiver.yaml index 3ffc661..1d22509 100644 --- a/clusters/production/webhook-receiver.yaml +++ b/clusters/production/webhook-receiver.yaml @@ -6,9 +6,12 @@ metadata: name: gitea-receiver namespace: flux-system spec: - type: gitea - events: - - push + # 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: