Skip to content

feat: operator auto-detects version for controller/router image defaults#844

Draft
mangelajo wants to merge 1 commit into
mainfrom
worktree-operator-version-detect
Draft

feat: operator auto-detects version for controller/router image defaults#844
mangelajo wants to merge 1 commit into
mainfrom
worktree-operator-version-detect

Conversation

@mangelajo

Copy link
Copy Markdown
Member

Summary

  • The operator now resolves :latest image defaults to its own version tag at runtime (e.g. :0.9.0, :0.9.0-rc.1)
  • Uses the existing build-time version injected via ldflags (-X main.version=$(GIT_VERSION))
  • Admin overrides with explicit image tags pass through unchanged
  • Dev builds (version="dev") preserve :latest as-is
  • Eliminates the need to manually update kubebuilder defaults in jumpstarter_types.go during releases

Test plan

  • Verify operator logs its version at startup
  • Deploy with a tagged operator image → controller/router deployments should use matching version tag
  • Deploy with :latest operator (dev build) → controller/router should also use :latest
  • Set explicit image override in CR → operator should respect the override, not replace it

🤖 Generated with Claude Code

…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>
@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@mangelajo, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2a9b9c17-367c-400c-bd47-c188f568ad4c

📥 Commits

Reviewing files that changed from the base of the PR and between 26aee22 and 52d35e7.

📒 Files selected for processing (2)
  • controller/deploy/operator/cmd/main.go
  • controller/deploy/operator/internal/controller/jumpstarter/jumpstarter_controller.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch worktree-operator-version-detect

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mangelajo mangelajo marked this pull request as draft June 26, 2026 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant