fix: Bump operator chart and image versions to latest

[danielpanzella]

Summary by CodeRabbit

• Chores
  • Updated default operator chart version to 1.4.2.
  • Updated default controller image tag to 1.20.0.

[coderabbitai]

Walkthrough

The default values for two deployment-related variables in the Terraform configuration were updated: operator_chart_version now defaults to "1.4.2" and controller_image_tag now defaults to "1.20.0". No other modifications were made to the variable definitions or their metadata.

Changes

File	Change Summary
variables.tf	Updated default values for operator_chart_version and controller_image_tag variables.

Poem

A hop and a skip, new versions appear,
Operators and controllers, both shifting gear.
From 1.3.4 to 1.4.2 we leap,
And 1.14.0 to 1.20.0, the change is deep.
With carrots in paw, the code’s up to date—
Hooray for progress, let’s celebrate! 🥕

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 921e38f and 61d774f.

📒 Files selected for processing (1)

• variables.tf (1 hunks)

🔇 Additional comments (2)

variables.tf (2)

30-33: Confirm that chart 1.4.2 is published and compatible with the targeted K8s & Helm versions.

Hard-pinning an operator chart to a version that is not yet published or is incompatible with the cluster/Helm version will break new installs. Please double-check that:

1. wandb-operator (or the chart repo you consume) actually contains 1.4.2.
2. Release notes do not list breaking changes that require additional values or CRD upgrades.

If you have CI that installs the module, consider adding an acceptance test that resolves the chart URL to catch this early.

---

36-39: Verify the controller_image_tag = "1.20.0" exists in the image registry and is required by chart 1.4.2.

Mismatch between the chart’s appVersion and the default image tag can lead to a failed rollout (e.g., wrong CRD schema). Confirm that:

• docker pull <registry>/wandb-controller:1.20.0 succeeds.
• The chart’s values file (or values.yaml diff) references the same default tag, or you override it consistently elsewhere in the module.

If you need help wiring a smoke test into CI to pull & inspect the image manifest, let me know.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[jsbroks]

This PR is included in version 7.14.3 🎉