kacerrandClaude Opus 5 1c773c24ad Add the cluster-scoped ProviderHealth CRD ...

One operator-owned object per configured provider will carry the
periodic check result: a Ready condition, per-target verdicts with their
own transition times, and a ready/total count for kubectl get. There is
no spec; only a viewer role is shipped since the operator is the sole
writer. Written by hand (kubebuilder is not installed), registered in
the existing AddKnownTypes call rather than a second init().

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-11 18:30:31 +00:00

..

crawl.example.com_providerhealths.yaml

Add the cluster-scoped ProviderHealth CRD

2026-09-11 18:30:31 +00:00

crawl.example.com_proxies.yaml

Add Proxy API types with CEL validation (Step 1)

2026-08-07 21:01:56 +02:00