Merge 0.0.6 mvp_demo to main

[shreyabiradar07]

Merge 0.0.6 release from mvp_demo to main branch

Summary by Sourcery

Update kruize-operator to version 0.0.6 with refreshed images, tooling, and documentation for the new release.

Enhancements:

• Bump Go toolchain and multiple Go module dependencies, including Prometheus, OpenTelemetry, golang.org/x, gRPC, and protobuf, to newer versions.
• Update default autotune image tag and sample manifests to use the latest Kruize Autotune release.
• Refresh operator metadata and image tags to reference kruize-operator v0.0.6 across manifests and constants.

Build:

• Update builder and runtime base images in Dockerfiles and set the default VERSION to 0.0.6 in the Makefile.

CI:

• Enhance the sync-kruize-versions workflow to accept a configurable base branch input and default it to mvp_demo.

Documentation:

• Revise README and CSV documentation to require Go 1.25.0+ and clarify recommended resource and storage configuration across cluster types.

[sourcery-ai]

Reviewer's Guide

Bumps the operator to version 0.0.6, aligning Go/toolchain, base images, manifests, docs, and GitHub automation with the new release and newer upstream libraries.

File-Level Changes

Change	Details	Files
Upgrade Go toolchain and Go module dependencies to newer versions.	Increase Go language version from 1.24.0 to 1.25.0 in go.mod Update Go toolchain version from go1.24.7 to go1.25.9 in go.mod Bump cel.dev/expr, Prometheus, OpenTelemetry, golang.org/x/, and google.golang.org/ dependencies to newer releases in go.mod Regenerate go.sum to match updated dependencies	go.mod go.sum
Update operator, bundle, and sample manifests to use the 0.0.6 operator and 0.10 autotune image, and clarify optional resource/storage configuration.	Update containerImage, name, version, createdAt, and manager image tags in CSV manifests from 0.0.5 to 0.0.6 Change default autotune image tag from 0.9 to 0.10 in manifests and constants Clarify documentation in CSV descriptions about optional resource/storage fields applying to all cluster types with recommendations per environment Update kustomization to point controller image tag to 0.0.6 Align sample Kruize CR to use autotune_operator:0.10	bundle/manifests/kruize-operator.clusterserviceversion.yaml config/manifests/bases/kruize-operator.clusterserviceversion.yaml config/manager/kustomization.yaml config/samples/v1alpha1_kruize.yaml internal/constants/kruize_images.go
Refresh Docker build and runtime base images and default operator version.	Update builder base image to ubi10/go-toolset:1.25.9 Update runtime base image in Dockerfile and bundle.Dockerfile to newer ubi10/ubi-minimal tag Bump default VERSION make variable from 0.0.5 to 0.0.6	Dockerfile bundle.Dockerfile Makefile
Improve the version sync GitHub Actions workflow to allow explicitly choosing the target base branch.	Add workflow_dispatch input base_branch with default mvp_demo Use inputs.base_branch (falling back to mvp_demo) instead of github.ref_name when computing BASE_BRANCH for branch creation and PR creation steps	.github/workflows/sync-kruize-versions.yml
Update project documentation for the newer Go toolchain.	Change README build requirements to Go v1.25.0+ and note security patch motivation	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• There are multiple hard-coded version strings for the operator and related images (e.g., 0.0.6, autotune 0.10) across manifests, samples, constants, and the Makefile; consider centralizing these in a single source (or a small set of well-defined sources) to reduce the risk of version drift in future bumps.
• In .github/workflows/sync-kruize-versions.yml, the default BASE_BRANCH is hard-coded to mvp_demo even for scheduled runs; consider deriving the default from the triggering ref or validating/overriding it per use case so the workflow behaves correctly when run against other branches (e.g., main).

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- There are multiple hard-coded version strings for the operator and related images (e.g., 0.0.6, autotune 0.10) across manifests, samples, constants, and the Makefile; consider centralizing these in a single source (or a small set of well-defined sources) to reduce the risk of version drift in future bumps.
- In `.github/workflows/sync-kruize-versions.yml`, the default `BASE_BRANCH` is hard-coded to `mvp_demo` even for scheduled runs; consider deriving the default from the triggering ref or validating/overriding it per use case so the workflow behaves correctly when run against other branches (e.g., `main`).

## Individual Comments

### Comment 1
<location path="go.mod" line_range="67-68" />
<code_context>
-	go.opentelemetry.io/otel v1.35.0 // indirect
+	go.opentelemetry.io/auto/sdk v1.2.1 // indirect
+	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.68.0 // indirect
+	go.opentelemetry.io/otel v1.43.0 // indirect
 	go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.34.0 // indirect
 	go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.34.0 // indirect
-	go.opentelemetry.io/otel/metric v1.35.0 // indirect
</code_context>
<issue_to_address>
**issue (bug_risk):** OpenTelemetry core and exporter versions are out of sync and may introduce subtle runtime issues.

Core OTel packages are now at v1.43.0 while the OTLP trace exporters remain at v1.34.0. OTel recommends keeping all components on the same major+minor version to avoid API/behavior mismatches. Please either upgrade the exporters to v1.43.0 or keep all OTel modules aligned on a single version.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[chandrams]

LGTM