Skip to content

build(deps): update Kruize image versions - #164

Open
kruize-version-sync[bot] wants to merge 1 commit into
mvp_demofrom
automated/bump-kruize-versions-36-1
Open

kruize-version-sync[bot] wants to merge 1 commit into
mvp_demofrom
automated/bump-kruize-versions-36-1

Conversation

@kruize-version-sync

@kruize-version-sync kruize-version-sync Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Automated Version Update

Updates Kruize image versions from upstream repositories.

Autotune: 0.11 → 0.11.2
UI: 0.1.0 → 0.1.0

  • Images verified on quay.io ✓

Summary by Sourcery

Enhancements:

  • Update the default and sample Kruize Autotune image from version 0.11.1 to 0.11.2.

Signed-off-by: kruize-version-sync <2884050+kruize-version-sync[bot]@users.noreply.github.com>
@sourcery-ai

sourcery-ai Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Kruize Autotune image references from 0.11.1 to 0.11.2 in both the sample configuration and the operator default, while leaving the UI and optimizer image versions unchanged.

File-Level Changes

Change Details Files
Updates the default Kruize Autotune container image from 0.11.1 to 0.11.2.
  • Changes the sample custom resource to reference the verified quay.io Autotune image tag 0.11.2.
  • Updates the operator’s default Autotune image tag constant to keep generated/default deployments aligned.
config/samples/v1alpha1_kruize.yaml
internal/constants/kruize_images.go

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 2 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="config/samples/v1alpha1_kruize.yaml" line_range="11" />
<code_context>
   # Supported values: "openshift", "minikube", "kind"
   cluster_type: "openshift"
-  autotune_image: "quay.io/kruize/autotune_operator:0.11.1"
+  autotune_image: "quay.io/kruize/autotune_operator:0.11.2"
   autotune_ui_image: "quay.io/kruize/kruize-ui:0.1.0"
   optimizer_image: "quay.io/kruize/kruize-optimizer:0.0.1"
</code_context>
<issue_to_address>
**OLM examples deploy old image**

When an OLM user creates a Kruize resource from the CSV's embedded example, the CSV's `alm-examples` still sets `autotune_image` to `quay.io/kruize/autotune_operator:0.11`; `deployKruizeComponents` passes that explicit value instead of applying the new default, so the resource deploys the older Autotune image.

Update the CSV's embedded `alm-examples` to use `quay.io/kruize/autotune_operator:0.11.2`.
</issue_to_address>

### Comment 2
<location path="internal/constants/kruize_images.go" line_range="36" />
<code_context>
 const (
 	// defaultAutotuneImageTag is the default tag for Kruize Autotune image
-	defaultAutotuneImageTag = "0.11.1"
+	defaultAutotuneImageTag = "0.11.2"

 	// defaultUIImageTag is the default tag for Kruize UI image
</code_context>
<issue_to_address>
**Existing installs keep old Autotune**

When an existing installation upgrades the operator and its Kruize CR leaves `autotune_image` empty, `NewKruizeResourceGenerator` builds the Deployment with the new default image, but `reconcileNamespacedResource` returns without updating an existing Deployment. Upgraded installations therefore keep running the old Autotune image despite the new default.

Update existing generated resources when their desired spec changes, or otherwise trigger their replacement during the image-version upgrade.
</issue_to_address>

Sourcery assessment

Approval pending. 2 findings to address first.

Blocking findings: config/samples/v1alpha1_kruize.yaml:11, internal/constants/kruize_images.go:36


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

# Supported values: "openshift", "minikube", "kind"
cluster_type: "openshift"
autotune_image: "quay.io/kruize/autotune_operator:0.11.1"
autotune_image: "quay.io/kruize/autotune_operator:0.11.2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · OLM examples deploy old image

When an OLM user creates a Kruize resource from the CSV's embedded example, the CSV's alm-examples still sets autotune_image to quay.io/kruize/autotune_operator:0.11; deployKruizeComponents passes that explicit value instead of applying the new default, so the resource deploys the older Autotune image.

Update the CSV's embedded alm-examples to use quay.io/kruize/autotune_operator:0.11.2.

Prompt for AI agents
In `config/samples/v1alpha1_kruize.yaml` at line 11:

**OLM examples deploy old image**

When an OLM user creates a Kruize resource from the CSV's embedded example, the CSV's `alm-examples` still sets `autotune_image` to `quay.io/kruize/autotune_operator:0.11`; `deployKruizeComponents` passes that explicit value instead of applying the new default, so the resource deploys the older Autotune image.

Update the CSV's embedded `alm-examples` to use `quay.io/kruize/autotune_operator:0.11.2`.

const (
// defaultAutotuneImageTag is the default tag for Kruize Autotune image
defaultAutotuneImageTag = "0.11.1"
defaultAutotuneImageTag = "0.11.2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · Existing installs keep old Autotune

When an existing installation upgrades the operator and its Kruize CR leaves autotune_image empty, NewKruizeResourceGenerator builds the Deployment with the new default image, but reconcileNamespacedResource returns without updating an existing Deployment. Upgraded installations therefore keep running the old Autotune image despite the new default.

Update existing generated resources when their desired spec changes, or otherwise trigger their replacement during the image-version upgrade.

Prompt for AI agents
In `internal/constants/kruize_images.go` at line 36:

**Existing installs keep old Autotune**

When an existing installation upgrades the operator and its Kruize CR leaves `autotune_image` empty, `NewKruizeResourceGenerator` builds the Deployment with the new default image, but `reconcileNamespacedResource` returns without updating an existing Deployment. Upgraded installations therefore keep running the old Autotune image despite the new default.

Update existing generated resources when their desired spec changes, or otherwise trigger their replacement during the image-version upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants