chore(deps): update istio to v1.31.1 and move charts to blob.istio.io #58
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
homelab/core!58
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/istio-1.31"
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?
Why
Istio 1.31 is the prerequisite for the K3s upgrade campaign (1.33.4 → 1.37): Istio 1.30 supports Kubernetes 1.32–1.36 only, 1.31 adds 1.37. Runbook:
docs/k3s-upgrade.mdin the homelab base repo.What
https://blob.istio.io/istio-release/chartshttps://blob.istio.io/istio-release/chartshttps://blob.istio.io/istio-release/chartsFrom 1.31 the charts are only published at blob.istio.io; the old
istio-release.storage.googleapis.comindex stops at 1.30.5, which is why Renovate never offered the minor. The GCP endpoints are scheduled for retirement with scream tests until 2026-12-09.Checks
helm lint charts/core charts/shared: cleaningressService/ingressSelectorand the DNS-capture proxyMetadata; gateway keeps all five ports; base renders 15 CRDs.registry.istio.io/releasetodocker.io/istio(chart default, three images).istio-ingress/gatewaypods carry a proxy; no sidecar fleet to restart.1.31 upgrade notes reviewed
OutlierDetection.minHealthPercentis set (PILOT_AUTO_SEND_UNHEALTHY_ENDPOINTS). Two DestinationRules in the mesh; watch gateway routing after sync.PILOT_SPAWN_UPSTREAM_SPAN_FOR_GATEWAYremoved (not set here).After merge
Monitor
istio-base,istiod,gatewayApplications to 1.31.1 Synced/Healthy, confirmistiodand both gateway pods run 1.31.1, then probe the four ServiceLB endpoints (gateway 80/443/18080/18443, forgejo-ssh 2206, mqtt 1883, pihole-dns 53).