Repository navigation
Replace the temporary archived MinIO test server with a maintained distribution #4326
Description
🤖 Generated by the Agentic Engineer
The disposable S3 test fixture relies temporarily on a digest-pinned community MinIO build from Bitnami Legacy. The previous official server repository refuses anonymous pulls, while the current AIStor server requires a license before serving S3. Production backup storage remains Cloudflare R2.
Bitnami Legacy is an unsupported archive and receives no security updates. Its continued availability is not a maintenance guarantee. The test fixture needs a maintained, reproducible distribution rather than an indefinite archive dependency.
Acceptance criteria:
- Choose a maintained community distribution or build and publish a reviewed, reproducible server image in the owning Platform repository.
- Preserve non-root execution, a read-only filesystem, file-mounted credentials and disposable test storage.
- Prove ordinary S3 keys still work for the Velero/CNPG paths and pass the protected Wedding bootstrap workflow.
- Remove the archived image from the local provider and fixture without introducing an unapproved account or license requirement.
Related: #4325. Vendor context: Bitnami archive policy and AIStor licensing behavior.
Metadata
Metadata
Assignees
Type
Fields
No fields configured for Security.
Projects
- Status
Activity
devantler commentedon Oct 1, 2026
The protected main-only backup bootstrap proof passed again after the July archived-server update merged. Run 36895746317, source commit
33488c941e4ce750bc3c2aecf46293ee0c73d57d, completed successfully at 2026-10-01 16:59:07 UTC. It verified empty-store seeding, periodic reseeding, storage access using only projected fixture credentials, and cleanup; an independent readback confirmed the fixture resources were absent.The earlier assumption that this server rejects the 16-character generated fixture secret was disproved by this successful live proof and a disposable local storage read/write check. The archived-server replacement remains open: passing the bootstrap path does not make an archived image a supported long-term dependency.
devantler commentedon Oct 1, 2026
Directly checked the reported short local access-key concern using disposable dummy storage on Linux ARM64 and the exact pinned July server and current MC image digests. The documented local-only five-character key and 28-character secret worked through the tracked file-backed server credentials and
mc alias importpath: bucket creation succeeded on the first attempt, PUT and GET returned identical data, LIST returned the exact sentinel, and object/bucket deletion succeeded. The client exited zero. Both containers, their internal network, dummy storage and mounted credential files were independently verified absent afterward.This contradicts the proposed local short-key incompatibility for these exact images and this documented credential shape. No encrypted payload or live credential was read, so it does not establish anything about the live backup credentials. The archived-server replacement remains open; successful compatibility testing does not make that image maintained.
chore: agent-claim #4326 nonce=5130755b6aed50f54e067f7f04791aab
devantler commentedon Oct 2, 2026
The maintained S3 fixture replacement is merged in PR #4346, commit
0161c8b89517f63b0e6748cb735d6bd134d803f8, at 2026-10-02 02:21:43 UTC. Queue CI and production deployment passed for that exact revision. A separate scoped readback confirms the signed OCI source is Ready and verified, and both resumed Flux roots have applied the digest published by that deployment.The protected main-only Wedding bootstrap acceptance run passed at 02:26:13 UTC, attempt 1, using that same merged source. Its receipt verifies empty-store credential seeding, periodic reseeding after the fixture copies were removed, storage access using only projected fixture credentials, and cleanup. This also exercised the direct-Pod network checks against the maintained server, with the management listener blocked and the S3 positive controls passing while the same server remained running.
The workflow's independent cleanup step passed. A separate read-only cluster check then confirmed both the disposable namespace and temporary controller network policy were absent. No production backup credential or database data was read by this fixture test; this acceptance does not claim restoration of live database contents.
The archived server is removed from the tracked local provider and protected fixture. The replacement remains digest-pinned, non-root, uses a read-only filesystem and file-mounted credentials, and requires no new account or license. Earlier ordinary-key tests passed PUT, GET, LIST, DELETE, multipart and range operations on both the baseline and maintained candidate. All acceptance criteria for #4326 are satisfied.