This release contains significant improvements and new bug fixes, particularly in the s3gw backing store. Notably, this release brings garbage collection, improved bucket listing, including filtering, and conditional GETs.

This release is meant for testing and feedback gathering. It is not recommended for production use.

Should a bug be found and not expected to be related with known issues, one should feel encouraged to file an issue in our Github repository.

Features​

• rgw/sfs: Query-based version listing
• rgw/sfs: Support conditional GETs
• rgw/sfs: New garbage collection implementation
• rgw/sfs: Change on-disk file format, add suffixes
• ui backend: Parity with operations required by UI

Fixes​

• rgw/sfs: Fix warnings after enabling more compilation flags
• rgw/sfs: Several code cleanup efforts
• rgw/sfs: use global part id for multipart parts

Breaking Changes​

• On-disk format for both metadata and data store have changed.

Known Issues​

This release contains significant improvements and new bug fixes. Notably, this release brings server-side encryption support, conditional copy object, improvement in profiling.

This release is meant for testing and feedback gathering. It is not recommended for production use.

Should a bug be found and not expected to be related with known issues, one should feel encouraged to file an issue in our Github repository.

Features​

• rgw/sfs: Add server-side encryption support
• rgw/sfs: Conditional copy object
• ui : Make use of the UI REST API to prevent CORS issues

Fixes​

• rgw/sfs: Improve sqlite connection handling
• rgw/sfs: Fix missing multipart etag
• rgw/sfs: Fix etag and mtime not being sent with copy object response
• rgw/sfs: Increase build error reporting
• rgw/sfs: Improve profiling (sqlite, garbage collection)
• ui: Prevent switching bucket retention mode from Compliance to Governance

Breaking Changes​

Known Issues​

This release contains significant improvements and new bug fixes. Notably, this release brings improved multipart and sqlite stability.

This release is meant for testing and feedback gathering. It is not recommended for production use.

Should a bug be found and not expected to be related with known issues, one should feel encouraged to file an issue in our Github repository.

Features​

• rgw/sfs: Improved SQLite WAL usage
• rgw/sfs: Improved disk usage when copying objects
• rgw/sfs: Improved testing
• ui: Various improvements

Fixes​

• rgw/sfs: Allow multiple delete markers
• rgw/sfs: Fix various multipart transactions
• rgw/sfs: Check number of file descriptors on start
• rgw/sfs: Updated bucket stats
• ui: unable to access UI due to admin ops verifying cert
• ui: The Show/Hide button must have at least one default value
• ui: Dropdown buttons are not rendered correct
• ui: Disable caching of index.html

Breaking Changes​

Known Issues​

This release contains various fixes and improvements in the backend. Most notably, error handling, multipart handling and internal bookkeeping of objects has improved.

This release is meant for testing and feedback gathering. It is not recommended for production use.

Should a bug be found and not expected to be related to the list below, one should feel encouraged to file an issue in our GitHub repository.

Features​

• rgw/sfs: Log SQLite error / warning messages
• rgw/sfs: Add SQLite retries and error handling
• rgw/sfs: Improve multipart handling
• ui backend: Add endpoints for user management
• ui backend: Add bucket management endpoints
• ui frontend: Allow creating admin users

Fixes​

• rgw/sfs: Fix Invalid argument exception on exit with telemetry off
• rgw/sfs: Fix delete bucket when not empty
• rgw/sfs: Abort on-going multiparts on bucket removal
• rgw/sfs: Fix bucket listing
• rgw/sfs: Various fixes to object state transitions
• ui frontend: Fix table header on zoom-in
• ui frontend: Fix bucket deletion dialogue in Administrator mode
• ui frontend: Fix creating keys for users

Breaking Changes​

• On-disk format for the metadata store changed

Known Issues​

This release contains numerous fixes for the UI and a refactoring of the object versioning implementation.

This release contains a number of changes to the internal data structures and metadata schema in preparation for a more streamlined versioning and multipart implementation. In addition to that, the UI received a number of bug fixes, quality of life improvements and a stylistic overhaul, including the logo and colorscheme. The UI also received a large number of end-to-end tests as well as an update to the Angular version.

This release cycle focused on architecture adjustments to the s3gw service's backend store (SFS), which will be reflected on upcoming releases.

This release focuses on stabilizing our continuous integration and release process. In this context, we have also addressed a number of issues that was affecting our testing framework when automatically triggered by CI.

This release adds lifecycle management, object locks (legal holds) and an updated version of the radosgw we use for the backend.

This release is meant for testing and feedback gathering. It is not recommended for production use.

This release contains a few new features in the backend an in the UI, including object locking.

Since the very first version, Epinio has made use of an internal S3 endpoint to store the user's projects in the form of aggregated tarballs.

This release contains a bunch of stability fixes in the backend, but also some new features in the UI. Most notably, the UI can now display prefixes as directories, bringing back some familiarity to its feel.

This release contains several notable features on the User Interface and on the Helm Chart, in addition to prefix support when listing objects and an updated version of the radosgw we use for the backend.

Introduction​

In this tutorial, we will walk through the setup of a single-node K3s Kubernetes cluster with Rancher, together with the S3 Gateway (s3gw) and a Longhorn PV (Persistent Volume). This guide will use Digital Ocean, but these instructions will likely work with other cloud providers as well.

This release contains several important changes to the UI and the charts as well as the backend. In addition to that multiple issues in documentation and build tools were fixed.

This release introduces some notable changes to Charts, together with UI improvements. As usual, we are improving the overall quality of the project by addressing issues to documentation, testing, UI and tools.

s3gw is an S3-compatible service focused on deployments in a Kubernetes environment backed by any PVC, including Longhorn. Since its inception, the primary focus has been on cloud native deployments. However, the s3gw can be deployed in a myriad of scenarios, provided some form of storage is attached.

This release adds several bug fixes, together with UI improvements. In addition, the documentation, testing and other have been improved.

This release adds several bug fixes, together with UI improvements. In addition, the documentation, testing and other have been improved.

This release adds several new features, together with UI improvements. In addition, the documentation, testing and other have been improved.

This release add a few small fixes to the last release, especially in the UI. In addition to that, testing and other development processes have improved quite a bit.

With v0.4.0 we introduce Object Versioning in the Gateway. Other than this, we are improving the project in almost all aspects, from the UI and Helm Charts to the Continuos Integration and Testing. Read the subsequent sections for all the changes in detail.

With v0.3.0 a few things changed in the overall project:

• the s3gw-core repository has been renamed s3gw-tools;
• the main repository is now [s3gw][1];
• the s3gw repository contains documentation and all other s3gw-related projects as submodules.

We are also releasing containers for s3gw and s3gw-ui with this version. Read below for more information.

Increased demand for cloud storage solutions has become a crucial topic in recent years: companies are requiring data to be made more readily available for their cloud-native applications.

The Aquarist Labs team is back with an open source and cloud-native S3 service. After spending months investigating a storage appliance built on Ceph, the team identified the need to complement the Rancher storage portfolio with their unique skillsets and lessons learned from their time developing Aquarium.