feat(container)!: Update image ghcr.io/home-operations/charts-mirror/llmkube (0.9.30 ➔ 0.10.0) #2244
No reviewers
Labels
No labels
area/bootstrap
area/ci
area/kubernetes
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
renovate/container
renovate/github-action
renovate/github-release
renovate/grafana-dashboard
renovate/helm
renovate/terraform
type/digest
type/major
type/minor
type/patch
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
GiorgioAresu/home-ops!2244
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/major-ghcr.io-home-operations-charts-mirror-llmkube-0.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.9.30→0.10.0Release Notes
defilantech/LLMKube (ghcr.io/home-operations/charts-mirror/llmkube)
v0.10.0Compare Source
⚠ BREAKING CHANGES
Features
Bug Fixes
Configuration
📅 Schedule: (in timezone Europe/Rome)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.
✅ Automated recommendation: APPROVE
Analysis engine: minimax/MiniMax-M2-7-anthropic@http://litellm.ai.svc.cluster.local:4000/v1 (anthropic)
Review: llmkube Chart 0.9.30 → 0.10.0
Recommendation: Approve
This is a straightforward OCI Helm chart version bump for the llmkube application. The single-line diff updates the
ref.tagfrom0.9.30to0.10.0in the OCIRepository resource.Change Summary
kubernetes/apps/ai/llmkube/app/ocirepository.yamltag: 0.9.30→tag: 0.10.0Standards Compliance
metadata.namespaceis intentionally omitted from OCIRepository, consistent with documented conventions.Breaking Change Caveat
The upstream release notes flag a breaking change ("metal-agent: serve engines on loopback behind an authenticated ingress"). This is an upstream chart concern — the change is limited to the chart version reference, and no HelmRelease values files were modified. If the authenticated ingress requires additional configuration or credentials in the HelmRelease, that would need to be addressed separately.
Evidence Summary
Non-blocking Note
The PR title includes the
!convention indicating a breaking change. Reviewers should be aware that if the llmkube HelmRelease requires value overrides to accommodate the upstream authentication change, those would need to be applied post-merge.4 resources changed across 2 apps · 1 CRD
Blast radius
Kustomization ai/llmkube: 1 dependent (ai/llmkube-models)ghcr.io/defilantech/llmkube-controller0.9.300.10.0konflate 0.6.4 · rendered
47d20b6· full diff →