Repository navigation
doc: point the local kind guide at our own MinIO build - #39149
Merged
ggevay merged 2 commits intoSep 25, 2026
Merged
Conversation
misc/helm-charts/testing/minio.yaml pulled quay.io/minio/minio, which no longer allows anonymous pulls, so every orchestratord workflow that applies it failed to start MinIO. Use materialize/minio, our own MinIO build published under each release tag. It has no `mc`, so a Job creates the `persist` and `bucket` buckets instead of the postStart hook. The service name, credentials and bucket are unchanged, so the persist_backend_url in released materialize.yaml files keeps working. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Released versions of persist cannot read multipart blobs from RustFS, because it omits the x-amz-mp-parts-count header (MaterializeInc#39115 fixes this, but no release has it yet). Following the guide on v26.42.0, any batch part over 8 MiB crashes environmentd or crash-loops a cluster with "Invalid Parquet file. Corrupt footer". Fetch minio.yaml from main, which now runs our own MinIO build, and drop the persist_backend_url edit, since the released materialize.yaml already points at MinIO. The documentation-defaults workflow follows the guide. Co-Authored-By: Claude Opus 5.5 <[email protected]>
ggevay
marked this pull request as ready for review
September 25, 2026 12:02
jubrad
approved these changes
Sep 25, 2026
ggevay
enabled auto-merge (squash)
September 25, 2026 12:14
This was referenced Oct 2, 2026
val-materialize
added a commit
that referenced
this pull request
Oct 9, 2026
Release notes for the v26.45 train, published as **v26.45.1**. v26.45.0 did not ship, so (as with v26.44) its notes are folded in here and [#39477](#39477) is closed unmerged. - **v26.45.0 content**: 8 Improvements, 2 Agent Skills, 8 Bug Fixes, copied verbatim from #39477 with anchors renamed to `{#v26.45.1-…}`. - **v26.45.1 content**: Alerting for Self-Managed and the external dependency monitoring Improvement (editor-added). The release's only PR, [#39659](#39659), is omitted. - **Dates**: Cloud 2026-10-08, Self-Managed 2026-10-09. The operator compatibility row is `v26.45.1`. `v26.45.md` (`patch: 1`, no `rc`) is already on `main`.⚠️ **Open questions** - **Group-sync bullet**: `oidc_group_role_sync_enabled` defaults to `false` at the tag. Is it on in Cloud? If not, cut the "Quieter logins" bullet. - **Certificate SAN requirements** ([#39316](#39316), [#39415](https://github.com/MaterializeInc/materialize/pull/39415)/[#39459](https://github.com/MaterializeInc/materialize/pull/39459)) need action at upgrade time but sit in Improvements. Should they be called out more loudly? Also, does [#39351](#39351) (S3 on rustls) impose the same SAN rule on custom S3 endpoints? - **[#39659](#39659) (omitted)**: is `enable_upsert_paged_spill` on in production? A draft bullet is in [omitted.md](https://github.com/MaterializeInc/mz-skills/blob/main/data/mz-release-notes/v26.45.1/final/omitted.md#borderline). - **`EXPLAIN ANALYZE ... CPU`**: [agent-skills#90](MaterializeInc/agent-skills#90) says it overstates joins, reductions, and TopK by 1.5x–3x before v26.46. Not published. Is that a known issue? - **Metric sinks**: [#39332](#39332), [#38910](#38910), and [#39337](#39337) are withheld because `enable_metric_sink` is `false`. #39337 fixes a panic any superuser can reach, so consider publishing it regardless. - **Possible cuts**: [#39362](#39362) was observed only in CI. The latency figures from [#39179](#39179) were measured on one noisy machine. - **Possible adds**: [#38894](https://github.com/MaterializeInc/materialize/pull/38894)–[#38896](https://github.com/MaterializeInc/materialize/pull/38896) (MV correction buffer) need an end-to-end number. [#39149](#39149) fixes the kind install guide, which crash-loops today. [#39549](#39549) (jemalloc page) is omitted because no released version had the regression. Snapshot drafts in mz-skills: [v26.45.0](https://github.com/MaterializeInc/mz-skills/tree/main/data/mz-release-notes/v26.45.0) (rc.1–rc.4, final), [v26.45.1](https://github.com/MaterializeInc/mz-skills/tree/main/data/mz-release-notes/v26.45.1/final). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude <[email protected]> Co-authored-by: Valerie Chiang <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #39125 (DEP-268).
Closes: QAR-194
Issue:
x-amz-mp-parts-count. persist: read multipart blobs from stores without x-amz-mp-parts-count #39115 fixes this, but no release has it yet. Following the current local kind guide on v26.42.0, any batch part over 8 MiB crashes environmentd or crash-loops a cluster withInvalid Parquet file. Corrupt footer.misc/helm-charts/testing/minio.yamlpullsquay.io/minio/minio, which no longer allows anonymous pulls, so the orchestratord nightly workflows cannot start MinIO.Solution:
testing/minio.yamlrunsmaterialize/minio:v26.42.0, our own MinIO build, which is published under every release tag. The image has nomc, so a Job creates the buckets instead of the postStart hook. The service name, credentials, and buckets are unchanged, so thepersist_backend_urlin releasedmaterialize.yamlfiles keeps working.minio.yamlfrommainand no longer asks users to editpersist_backend_url.workflow_documentation_defaultsfollows the guide again.Gotchas:
rustfs.yamlstays inmisc/helm-charts/testingfor the RustFS move once a release contains persist: read multipart blobs from stores without x-amz-mp-parts-count #39115.🤖 Generated with Claude Code