Skip to content

Releases: TFMV/featherman

v0.3.0

01 Jun 09:01
@TFMV TFMV
v0.3.0
b783811
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v0.3.0 Pre-release
Pre-release 
Merge pull request #16 from TFMV/feature/lake

.
Loading

v0.2.0

30 May 15:07
@TFMV TFMV
v0.2.0
6293e78
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v0.2.0 Pre-release
Pre-release

What's Changed

Full Changelog: v0.1.0...v0.2.0

Contributors

TFMV
Loading

v0.1.0

30 May 10:30
@TFMV TFMV
v0.1.0
40beabe
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v0.1.0 Pre-release
Pre-release

[0.1.0-pre] - 2025-05-30

This is the first pre-release of Featherman, a Kubernetes operator for DuckDB-powered data lakes. This release includes the core functionality for managing DuckDB catalogs and tables in Kubernetes.

Added

Core Features

  • Initial implementation of the DuckLake operator
  • Custom Resource Definitions (CRDs):
    • DuckLakeCatalog: Manages DuckDB catalog files and S3 storage configuration
    • DuckLakeTable: Defines table schemas and Parquet storage options

Backup Management

  • Automated backup system for DuckDB catalogs
  • Configurable backup scheduling with cron expressions
  • S3-compatible storage support for backups
  • Retention policy management for automated cleanup
  • Backup status tracking in catalog status

Storage Integration

  • S3-compatible object store integration
  • Support for custom endpoints and regions
  • Secure credential management through Kubernetes secrets
  • PVC-based catalog storage with size validation

Security

  • Validation webhooks for CRD configuration
  • Non-root container execution
  • Read-only root filesystem for jobs
  • Proper capability management
  • Secure AWS credential injection

Operational Features

  • Leader election for high availability
  • Health and readiness probes
  • Structured logging throughout the operator
  • Job-based execution model for reliability
  • Resource cleanup on deletion

Notes

This is a pre-release version intended for early testing and feedback. While core functionality is implemented, the following limitations apply:

  • Limited to S3-compatible storage backends
  • Basic monitoring and metrics
  • Documentation is work in progress
  • No upgrade path from this version
  • API may change in future releases

Known Issues

  • Backup retention cleanup may be delayed if the operator restarts during execution
  • Large catalog files (>10GB) may experience slower backup times
  • Table operations do not yet support concurrent modifications

For detailed installation and usage instructions, please refer to the README.md.

Loading