Storage Class

Installation Path in KubeDNA

You can deploy the appropriate StorageClass directly from the UI:

Path:
[Selected Cluster] > Components > Storage Class

• StorageClass components are pre-integrated per provider.

• Installation is fully automated and tailored to your cloud or on-prem environment.

☁️ Supported Providers & Their StorageClasses

🇳🇱 Leafcloud (Dutch Cloud Provider – OpenShift-based)

• StorageClass Name: leafcloud-block (OpenShift CSI-backed)

• Provisioner: Depends on OpenShift CSI integration (e.g. csi.trident.netapp.io)

• Features:

  • Fully OpenShift-compatible

  • Optimized for sustainability and energy-efficient compute

  • High IOPS performance for block workloads

• Recommended Usage: Cloud-native apps, container registries, and databases

🔷 Hetzner Cloud

• StorageClass Name: hcloud-volumes

• Provisioner: csi.hetzner.cloud

• Features:

  • Dynamic provisioning of volumes using Hetzner CSI driver

  • Resize and snapshot support

  • Cost-efficient high-performance storage

• Recommended Usage: Stateful apps, monitoring data, and persistent services

🔵 Microsoft Azure

• StorageClass Name: azure-disk (default) and azure-files (optional)

• Provisioner: disk.csi.azure.com / file.csi.azure.com

• Features:

  • SSD and HDD tiers (Standard_LRS / Premium_LRS)

  • Integrated with Azure zones and RGs

  • Encryption and resizing supported

• Recommended Usage:

  • azure-disk: Databases, stateful workloads

  • azure-files: Shared access (e.g. WordPress, NFS-style needs)

🟠 Amazon Web Services (AWS)

• StorageClass Name: gp2, gp3, or custom ebs-sc

• Provisioner: ebs.csi.aws.com

• Features:

  • Dynamic EBS volume provisioning

  • Multi-AZ support (with pod anti-affinity)

  • Supports snapshots, encryption, and resizing

• Recommended Usage: General stateful apps and data services

🟡 Google Cloud Platform (GCP)

• StorageClass Name: standard-rwo, premium-rwo

• Provisioner: pd.csi.storage.gke.io

• Features:

  • SSD or HDD persistent disks

  • Integrated GCP-native provisioning

  • Zonal and regional configurations

• Recommended Usage: High throughput apps, persistent caching, databases

📌 Notes

• All StorageClasses provisioned via KubeDNA follow Kubernetes best practices (e.g., reclaimPolicy: Delete, dynamic provisioning enabled).

• You can manually override default settings through Helm values or direct manifests if required.