feat: operator auto-detects version for controller/router image defaults#844
feat: operator auto-detects version for controller/router image defaults#844mangelajo wants to merge 1 commit into
Conversation
…e tags The operator now uses its build-time version (injected via ldflags from git describe) to resolve the default image tag for controller and router deployments. When the CR uses the :latest default, the operator replaces it with its own version tag at runtime (e.g. :0.9.0 or :0.9.0-rc.1). Admin overrides with explicit image tags are passed through unchanged. In dev builds (version="dev"), :latest is preserved as-is. This eliminates the need to manually update kubebuilder defaults in jumpstarter_types.go during every release. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 35 minutes and 56 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
## Summary - Adds a `/release` Claude Code skill that interactively guides through the full Jumpstarter release process: creating release branches, tagging releases (RC and final), and contributing operator bundles to community-operators - Enforces correct ordering (images must exist before bundle generation), RC-first policy for new branches, and `vX.Y.Z-rc.N` tag naming convention - Fixes operator release docs by removing the incorrect e2e_test.go update step (`defaultControllerImage` uses `:latest`, not a pinned version) ### Improvements from real v0.9.0-rc.1 release: - Removed `jumpstarter_types.go` update step (operator resolves image tags at runtime via jumpstarter-dev#844) - Added `AUTO_CONFIRM=1` for non-interactive `make contribute` - Added `gh pr create` commands for community-operators PRs - Added branch protection ruleset reminder for new release branches - Added `gh run rerun` suggestion on CI failure - Documented API fallback for creating protected release branches ## Test plan - [x] Successfully used to release v0.9.0-rc.1 - [ ] Verify `/release` loads and asks the right initial questions - [ ] Dry-run each scenario: new branch, RC tag, final tag, operator bundle 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Summary
:latestimage defaults to its own version tag at runtime (e.g.:0.9.0,:0.9.0-rc.1)-X main.version=$(GIT_VERSION))version="dev") preserve:latestas-isjumpstarter_types.goduring releasesTest plan
:latestoperator (dev build) → controller/router should also use:latest🤖 Generated with Claude Code