ksops fails the whole sops-secrets application on this file: it targets namespace forgejo, which does not exist. That failure blocks every other file in the generator, including zitadel-masterkey.
The same Secret name is generated in namespace api by forgejo-registry-pat-api.enc.yaml, and the gateway reads that copy. Forgejo runs in namespace cicd.
ksops fails the whole sops-secrets application on this file: it targets namespace `forgejo`, which does not exist. That failure blocks every other file in the generator, including `zitadel-masterkey`.
The same Secret name is generated in namespace `api` by `forgejo-registry-pat-api.enc.yaml`, and the gateway reads that copy. Forgejo runs in namespace `cicd`.
ksops failed the whole sops-secrets application on this file: it declares
Secret forgejo-registry-pat in namespace forgejo, and no such namespace exists.
The failure blocks every other file in the generator list, including
zitadel-masterkey.
The same Secret name is already generated in namespace api by
forgejo-registry-pat-api.enc.yaml, and that is the copy the gateway reads. The
forgejo namespace copy is stale: Forgejo runs in namespace cicd, and namespace
forgejo was never created.
Remove the file and its generator entry. ArgoCD never created the Secret, so
pruning has nothing to remove.
rock
merged commit 6c98ca7436 into main2026-10-24 10:47:24 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
ksops fails the whole sops-secrets application on this file: it targets namespace
forgejo, which does not exist. That failure blocks every other file in the generator, includingzitadel-masterkey.The same Secret name is generated in namespace
apibyforgejo-registry-pat-api.enc.yaml, and the gateway reads that copy. Forgejo runs in namespacecicd.