What This Design Does:

Dremio (OSS) deployed on Kubernetes via the official dremio_v2 Helm chart. This Design represents a baseline installation of the Dremio coordinator (master) and executors with Services, ConfigMaps/Secrets, and optional Ingress. Chart values are adjusted to use an S3-compatible distStorage to satisfy Dremio ≥21.0’s “no local distStorage” requirement. Import-only topology intended for reuse and customization in Meshery Kanvas; users can override values (resources, node selectors, Ingress/TLS, persistence) per cluster.

Caveats and Consideration:

• distStorage: Dremio ≥21.0 does NOT support 'local'. Set distStorage.type to aws/azure/gcp and provide bucket + credentials (S3/MinIO example included). • Credentials: Store access keys in Kubernetes Secrets (avoid plain text). Update fs.s3a.endpoint and path-style access if using MinIO. • Persistence: Ensure PVCs are provisioned for metadata and scratch space; validate StorageClass and access modes for your cluster. • Resources: Size coordinators/executors appropriately (e.g., coordinator ≥4Gi RAM; executors commonly ≥8Gi RAM). Tune CPU/memory/heap per workload. • Networking: Ingress is off by default; configure hostnames, TLS, and service type (NodePort/LoadBalancer) as required. • Version note: Imported from packaged chart `dremio-2.0.0.tgz` (dremio_v2). Adjust if you target a different chart release. • This Design captures chart structure for catalog sharing; deployment behavior depends on cluster-specific values (storage class, DNS, IAM, etc.).

Compatibility:



Recent Discussions with "meshery" Tag