Repository navigation
build(deps): update Kruize image versions - #160
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 PR synchronizes the sample configuration and runtime defaults to use the verified Kruize Autotune image tag 0.11.2, with no change to the UI or optimizer image versions. 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 older Autotune**
When an OLM user creates a Kruize resource from the bundled CSV example, the CSV `alm-examples` sets `autotune_image` to `quay.io/kruize/autotune_operator:0.11` explicitly, so `NewKruizeResourceGenerator` keeps that value instead of using the updated fallback. The resource deploys the older image rather than 0.11.2.
Update the bundled CSV `alm-examples` to set `autotune_image` to `quay.io/kruize/autotune_operator:0.11.2`.
Also at `internal/constants/kruize_images.go:36`.
</issue_to_address>Sourcery assessment
Needs a human reviewer. 1 finding to address first, and if the 0.11.2 image is faulty or incompatible, the operator could deploy workloads that fail or behave incorrectly. Reverting the tag and rolling out the previous image can repair the affected runtime, although any outage or incorrect behavior before rollback would already have occurred.
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 older Autotune
When an OLM user creates a Kruize resource from the bundled CSV example, the CSV alm-examples sets autotune_image to quay.io/kruize/autotune_operator:0.11 explicitly, so NewKruizeResourceGenerator keeps that value instead of using the updated fallback. The resource deploys the older image rather than 0.11.2.
Update the bundled CSV alm-examples to set autotune_image to quay.io/kruize/autotune_operator:0.11.2.
Also at internal/constants/kruize_images.go:36.
Prompt for AI agents
In `config/samples/v1alpha1_kruize.yaml` at line 11:
**OLM examples deploy older Autotune**
When an OLM user creates a Kruize resource from the bundled CSV example, the CSV `alm-examples` sets `autotune_image` to `quay.io/kruize/autotune_operator:0.11` explicitly, so `NewKruizeResourceGenerator` keeps that value instead of using the updated fallback. The resource deploys the older image rather than 0.11.2.
Update the bundled CSV `alm-examples` to set `autotune_image` to `quay.io/kruize/autotune_operator:0.11.2`.
Also at `internal/constants/kruize_images.go:36`.
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: