build(deps): Bump github.com/go-faster/fs from 0.13.1 to 0.15.0

[dependabot]

Bumps github.com/go-faster/fs from 0.13.1 to 0.15.0.

Release notes

Sourced from github.com/go-faster/fs's releases.

v0.15.0

• Access keys created through the admin API are cluster-wide. They live in the replicated metadata, so every node accepts a key within seconds of its creation through any node. admin.keys_file is gone, and a config that sets it is refused (#345). New metrics: fs.auth.keys.refresh_age and fs.auth.keys.managed.
• A layout apply answers with the versions it retained, so a client reading it doesn't take a change in transition for a finished one (#343).

Changelog

New Features

• 9ac360e05bd070c40721bad77e9f481c05df5b8b: feat(auth): access keys created through the admin API are cluster-wide (@​ernado)

Bug fixes

• 09662ce1b0c1daa262d4c234b45197be6ee17860: fix(admin): a layout apply answers with the versions it retained (@​ernado)

Documentation updates

• 2cc7eb559c96ac4772e4e7ee43d8ecabcf55ef54: docs: drop the upgrade notes (@​ernado)

Docker images

docker pull ghcr.io/go-faster/fs:v0.15.0

v0.14.1

A bug-fix release on top of v0.14.0.

• A layout change no longer stalls for the sync interval. The first anti-entropy sweep under a new layout often fails briefly: a peer hasn't adopted the layout yet, or gossip hasn't spread a joining node's address. A failed sweep used to wait for the next sync_interval tick, 10 minutes by default. During that time older layout versions stayed retained, and a node being removed had to keep running. A failed sweep now retries after 5s, backing off to the interval (#342). The fs-operator e2e suite found this.

No config change. Upgrade from v0.14.0 is a rolling restart.

Changelog

Bug fixes

• e76462ecc8598ad23419f56c6eb99fa97c009834: fix(engine): retry a failed sweep soon, not a sync interval later (@​ernado)

Documentation updates

• 84d923caf12a1a2e65f7307c75cef544bd79a65a: docs(config): repair two doubled comments (@​ernado)

Docker images

docker pull ghcr.io/go-faster/fs:v0.14.1

v0.14.0

A rewrite toward a small, Garage-style object store: one storage engine for a single node and a cluster, about half the code of v0.13. Not an in-place upgrade — read the upgrade notes first.

Upgrade notes — breaking

• Data from v0.13 is not read. The filesystem backend is gone; the engine is the only storage. A node started on a v0.13 data directory refuses to start and says so. Copy your objects out with v0.13 and into a new storage root with v0.14, using any S3 client (mc mirror, aws s3 sync, rclone sync).
• Cluster mode is redesigned and does not upgrade in place. etcd, the sharded metadata plane, disks/placement and the scrubber are gone. A cluster is now a Garage-style layout over peer nodes: cluster: {node_id, addr, advertise_addr, peers, secret}, roles applied with fs layout apply. Build a new cluster and copy objects into it. All nodes of a cluster must run the same release.
• Config is strict. A key this release does not know — including every removed section (etcd, disks, integrity, metadata, rebalance, ...) — stops the server with an error naming it. Remove them.
• Helm chart: its config keys are now the server's (read_timeout, health_path, enable_metrics, ...). In earlier charts those settings were silently ignored; they now take effect.
• The admin web UI is gone; the admin API remains (access keys, reload, cluster layout and nodes, bucket scheme, key rotation).
• SSE-C over plain HTTP is refused, as on AWS; terminate TLS in front (or set encryption.customer_keys_over_http for development).

Highlights

... (truncated)

Commits

• 000226f Merge pull request #345 from go-faster/feat/replicated-keys
• 9ac360e feat(auth): access keys created through the admin API are cluster-wide
• 974a33b Merge pull request #344 from go-faster/docs/drop-upgrade-notes
• 2cc7eb5 docs: drop the upgrade notes
• 1709ee7 Merge pull request #343 from go-faster/fix/apply-layout-retained
• 09662ce fix(admin): a layout apply answers with the versions it retained
• cafb402 Merge pull request #342 from go-faster/fix/sweep-retry
• e76462e fix(engine): retry a failed sweep soon, not a sync interval later
• acd3644 Merge pull request #340 from go-faster/fix/config-comments
• 84d923c docs(config): repair two doubled comments
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!