Bundled Garage (evaluation only)
The in-cluster S3-compatible store bundled for evaluation - how to use it and its limits.
For evaluation, Eddytor can bundle Garage -
an S3-compatible object store by Deuxfleurs (AGPLv3), shipped unmodified. A bucket
(EDDYTOR_BUCKET, default eddytor) is created on boot so you can make tables
immediately.
Heads up
Register it
The credentials are the random GARAGE_ACCESS_KEY / GARAGE_SECRET_KEY the
installer wrote to .env. Register the bundled bucket against the in-cluster
endpoint:
eddytor create storage s3 --bucket eddytor \
--endpoint http://garage:3900 --region us-east-1 \
--access-key-id "$GARAGE_ACCESS_KEY" --secret-access-key "$GARAGE_SECRET_KEY"http://garage:3900 is the in-cluster S3 endpoint the engine uses.
The endpoint is the in-cluster Service name eddytor-garage:3900 (not
garage:3900), and the creds are the chart's demo defaults
(garage.accessKey / garage.secretKey - override for real use):
eddytor create storage s3 --bucket eddytor \
--endpoint http://eddytor-garage:3900 --region us-east-1 \
--access-key-id GK00000000000000000000000000000000 \
--secret-access-key 0000000000000000000000000000000000000000000000000000000000000000helm install … --set garage.bundled=true prints these commands in its NOTES.
No console, no shell
Garage has no web console (that was a MinIO feature), and the bundled image is
scratch - only the /garage binary, no shell - so you can't exec in to browse
data. Manage tables through Eddytor instead, which keeps the object store and
Eddytor's metadata in sync:
# delete a table (catalog is always `eddytor`); needs the TABLES_DELETE scope
eddytor delete table eddytor <schema> <table>For truly orphaned data Eddytor no longer tracks, see Managing & deleting at the S3 layer.