SourceRefNotYetSupported

Symptom
READY=False, REASON=SourceRefNotYetSupported.
Cause
The snippet sets spec.sourceRef but the operator was built without a Fetcher wired in. This is a mis-deployment in practice — production binary always wires sources.New(). Seeing this in a real cluster means you’re running:
- a test/dev binary
- a custom build where
defaultBuilderwas modified - a future code path that hasn’t enabled sourceRef yet
Diagnosis
kubectl logs deploy/jaas | grep -i "fetcher"
If the operator logs no Fetcher initialization, the binary is incomplete.
Remediation
Use a release binary, or convert the snippet to spec.files inline as a temporary workaround.