chore: update minio for seaweedfs in the docs by jeduardo · Pull Request #623 · syntasso/kratix-docs

jeduardo · 2026-08-19T13:43:09Z

Description

This relates to issue https://github.com/syntasso/kratix-private/issues/195 and changes all references to Minio to point to SeaweedFS instead. It includes documentation for Kratix OSS, SKE, and workshop setup procedures.

Checklist

Is this PR about a feature in an upcoming SKE release?
Have you cut that new SKE release?
Have you updated the release notes?

The quickstart, workshop and install guides all described a MinIO deployment in kratix-platform-system, a create-bucket Job to wait on, and the `mc` CLI. None of those exist any more: SeaweedFS runs in its own `seaweedfs` namespace behind a Service called `bucket`, the bucket is created by a helper container in the same Pod (so Pod readiness already means the bucket exists), and the repository ships a preconfigured `bin/s5cmd` instead of asking you to install a client. Substitutions throughout for the new endpoint, secret name and credentials. Sample listings of kratix-platform-system lose their state store line rather than gain a renamed one, since it is no longer in that namespace. The workshop's Terraform still uses the aminueza/minio provider: MINIO_ENDPOINT, minio_s3_bucket and friends are that provider's own interface, not our naming, so only the values around them change. Also fixes two `<TabItem value="minio">` entries that sat in the same groupId="stateStore" group as three pages already using value="bucket", which broke tab synchronisation between them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

… Kratix cannot install on Ran the workshop setup end to end against local kind clusters and compared every output. Fixes: - `bin/s5cmd ls` prints the `s3://` prefix; three outputs under `bin/s5cmd` commands were still in `mc` format, and one showed a bare bucket name. - `mc cat` survived one substitution; it is now `bin/s5cmd cat`. - The state store secret holds `kratixadmin`, so `describe secret` reports 11 bytes per key, not 10. - The canary documents are 90 and 181 bytes, not 116 and 206, and the namespace object no longer carries `creationTimestamp: null`. Separately, and not a SeaweedFS matter: the pinned `kindest/node:v1.27.3` cannot install the current released Kratix at all. Its CRDs use `selectableFields`, which needs Kubernetes 1.30 or newer, so `kubectl apply` of kratix.yaml fails with a strict decoding error and the workshop cannot proceed past that step. Bumped to v1.33.1, matching KIND_IMAGE in the Kratix repository's quick-start.sh. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

- Link SeaweedFS at the top-level repository rather than a wiki page, in both the state store reference and the quick start. - Point s5cmd at the coreweave fork; peak's is no longer maintained, and the Makefile already downloads coreweave's. - Add the missing check that SeaweedFS itself is running to the promise-writing guide. It sits in its own namespace, so the kratix-platform-system listing does not cover it; 2/2 also confirms the bucket exists, since the Pod is not Ready until it does. - Tighten the wording around the readiness check and the s5cmd step. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

senglezou and others added 2 commits August 19, 2026 12:57

jeduardo assigned jeduardo and senglezou Aug 19, 2026

senglezou reviewed Aug 19, 2026

View reviewed changes

Comment thread docs/main/03-reference/14-statestore/03-bucketstatestore.md Outdated