fix: regenerate CRD with optional tokenSecretRef #18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/crd-optional-tokenref"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The CRD was not regenerated when tokenSecretRef was made optional,
causing Flux dry-run validation to reject RunnerPools without it.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com
Automated review by pr-reviewer v0.15.0 | Safety Check | anthropic | tracking id
r-c623a1-0298adThis is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — The change correctly removes the required field constraint for tokenSecretRef and adds documentation explaining when it's optional.
Complexity: trivial
This is a straightforward CRD regeneration that removes
tokenSecretReffrom the required fields list and adds clarifying documentation. The change aligns with the PR description's goal of fixing Flux dry-run validation for RunnerPools that don't specify a token secret when using a global controller token. No security or logic concerns.