hetznercloud / csi-driver
Kubernetes Container Storage Interface driver for Hetzner Cloud Volumes
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing hetznercloud/csi-driver in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewContainer Storage Interface driver for Hetzner Cloud This is a Container Storage Interface driver for Hetzner Cloud enabling you to use ReadWriteOnce Volumes within Kubernetes & other Container Orchestrators. Please note that this driver **requires Kubernetes 1.19 or newer**. Kubernetes Docs • :rocket: See the getting started guide. • :book: See the CSI driver architecture for the involved components. Other Container Orchestrators **These environments are not officially supported**. However, thanks to their compatibility with the CSI spec and community contributions, quick start guides are available for the following: • Docker Swarm️ • HashiCorp Nomad️ Development Setup a development environment To setup a development environment, make sure you installed the following tools: • tofu • k3sup • docker • skaffold • Configure a in your shell session. > [!WARNING] > The development environment runs on Hetzner Cloud servers which will induce costs. • Deploy the development cluster: • Load the generated configuration to access the development cluster: • Check that the development cluster is healthy: • Start developing the CSI driver in the development cluster: On code change, skaffold will rebuild the image, redeploy it and print all logs from csi components. ⚠️ Do not forget to clean up the development cluster once are finished: Run the docker e2e tests To run the integrations tests, make sure you installed the following tools: • docker • Run the following command to run the integrations tests: Run the kubernetes e2e tests The Hetzner Cloud CSI driver is tested against the official kubernetes e2e tests. Before running the integrations tests, make sure you followed the Setup a development environment steps. • Run the kubernetes e2e tests using the following command: License MIT license