Repository navigation
build(deps): update Kruize image versions - #163
kruize-version-sync[bot] wants to merge 1 commit into
Conversation
Signed-off-by: kruize-version-sync <2884050+kruize-version-sync[bot]@users.noreply.github.com>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThe pull request aligns both the sample configuration and runtime default with the verified Kruize Autotune image tag 0.11.2; the UI image remains unchanged at 0.1.0. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Hey - I've found 1 issue
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 a user creates a Kruize resource from the bundled CSV example, the CSV’s `alm-examples` still sets `autotune_image` to `quay.io/kruize/autotune_operator:0.11`, and `NewKruizeResourceGenerator` passes that nonempty value through instead of using the new default, so the resource deploys the old image instead of `0.11.2`.
Update the CSV’s `alm-examples` to set `autotune_image` to `quay.io/kruize/autotune_operator:0.11.2`.
</issue_to_address>Sourcery assessment
Approval pending. 1 finding to address first.
Blocking findings: config/samples/v1alpha1_kruize.yaml:11
| # 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" |
There was a problem hiding this comment.
🟡 Medium · OLM examples deploy old image
When a user creates a Kruize resource from the bundled CSV example, the CSV’s alm-examples still sets autotune_image to quay.io/kruize/autotune_operator:0.11, and NewKruizeResourceGenerator passes that nonempty value through instead of using the new default, so the resource deploys the old image instead of 0.11.2.
Update the CSV’s alm-examples to set autotune_image to 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 a user creates a Kruize resource from the bundled CSV example, the CSV’s `alm-examples` still sets `autotune_image` to `quay.io/kruize/autotune_operator:0.11`, and `NewKruizeResourceGenerator` passes that nonempty value through instead of using the new default, so the resource deploys the old image instead of `0.11.2`.
Update the CSV’s `alm-examples` to set `autotune_image` to `quay.io/kruize/autotune_operator:0.11.2`.
Automated Version Update
Updates Kruize image versions from upstream repositories.
Autotune: 0.11 → 0.11.2
UI: 0.1.0 → 0.1.0
Summary by Sourcery
Enhancements: