Offer end-users a consistent and comprehensive view of their storage space as exposed via Storage Layer API specification.

Based on fork of https://github.com/filebrowser/filebrowser.

• adapt sharing logic incl. presigned urls
• create custom branding
• reflect read-only mode for content in UI
• connect to Storage Controller for dynamically build root with connected workspace buckets (injected via config)
• bundle together with Storage Layer microservice

Implement Storage Layer API specification.

Based on fork of https://github.com/filebrowser/filebrowser.

• replace local filesystem with s3 filesystem
• dynamically build root with connected workspace buckets (injected via config)
• bootstrap setup enabling read-only mode for content
• use proxy-header auth method for above bootstrap setup
• provide presigned url for selected content instead of proxying content as download
• adapt sharing capabilities to receive temporary link pointing to selected content
• create helm chart packaging bootstrap setup as additional init-container
• manually deploy on eoepca demo cluster with static setup for sign-off

Reconcile Storage CRDs and expose:

• Bucket credentials,
• Access URL,
• The current reconciliation state.

Define Workspace CRD specification allowing the Workspace controller to:

• Establish a dedicated namespace for each project/user in the Host Kubernetes cluster.
• Apply Kubernetes policies such as ResourceQuota, LimitRange, and NetworkPolicy to the namespace.
• Deploy a vCluster with best-practice configurations within the namespace.
• Create a new Git repository (or a folder in an existing Git repository, depending on the global setup) to store the desired manifests for - Workspace Services to be reconciled through Flux GitOps principles.
• Connect Flux to reconcile the Git repository (or folder) with the vCluster.
• Implement Kubernetes Validating Webhooks to enforce bucket creation policies, such as maximum number and size, and naming pattern conventions, within the namespace.

Define facade API facilitating a logical view on all physical storage and also the management of data itself.

Physical storage may either be dynamically provisioned (see Storage CRDs) or linked to existing.

Allow users to search and browse through the content of the storage buckets connected to a given workspace using directory-based file system semantics.

Allow sharing of specific content via pre-signed URLs, enabling direct HTTP access without requiring user authentication.

Reconcile Workspace CRDs and expose:

• vCluster credentials for direct “virtual” Kubernetes cluster access,
• Git settings used for Flux,
• The current reconciliation state.

Define Storage CRD specification allowing the Storage controller to:

• Establish a dedicated bucket or connect a federated bucket.
• Configure bucket access and CORS policies for the bucket.