Replace MinIO S3 with HDFS on Kubernetes Cluster for Fink Database Compatibility

[fjammes]

Goal of the Issue:
The goal of this issue is to replace the current MinIO S3 storage with Hadoop Distributed File System (HDFS) on the Kubernetes (K8s) cluster to ensure compatibility with the Fink database, which relies on HDFS for its data storage and access needs.

---

Describe the Issue
A short description of what the issue is:
While MinIO S3 is currently operational on the K8s cluster and meets general storage requirements, it needs to be replaced by HDFS to support the Fink database. The Fink database requires HDFS as its primary storage layer to enable seamless data operations and compatibility with its architecture.

Expected Behaviour
What you expected to happen:
HDFS should be deployed on the K8s cluster, providing a compatible and efficient storage layer for the Fink broker.

Actual Behaviour
What actually happened, error messages go here:
MinIO S3 is currently in use for object storage for hte Fink broker, but it does not fully support the HDFS-based architecture of the Fink database. No errors are currently present, but Fink database operations cannot be executed as expected on MinIO.

To Reproduce
Steps to replace MinIO S3 with HDFS:

1. Deploy HDFS on the Kubernetes cluster, using an appropriate procedure.
2. Configure access policies for HDFS to ensure smooth integration with the Fink broker.

Additional Context
The replacement of MinIO S3 with HDFS is necessary for Fink database operations, as the database relies on HDFS for optimal data handling and integration. HDFS is expected to offer the required compatibility, scalability, and high-throughput performance for Fink broker workloads on the Kubernetes cluster.