How yvosonthehub/labnetapp works
The LabNetApp project is a “lab” repository designed to help engineers and administrators learn about and experiment with NetApp’s Trident integration into Kubernetes clusters. It is not a production application per se; rather, it is a collection of labs (scenarios) that work across multiple Kubernetes versions (from v1 pre-CSI up to v6 with advanced CSI features) and that include both dynamic storage provisioning labs and application data protection (Trident Protect) use cases.
Main Components
• Kubernetes Cluster(s): Represented in the various “Kubernetes_v*” directories. Each version (v1, v2, v4, v5, v6) shows different labs and scenarios configured with appropriate Kubernetes manifests (pvc, pod, deployments, service definitions, etc.).
• Backend Storage Systems (ONTAP, SolidFire, etc.): Since the labs demonstrate dynamic provisioning for both NAS and SAN types, include representations of the physical storage backend (such as ONTAP) that works with Trident.
• Lab/Exercise Scripts and Supporting Tools: Although not a “runtime” component, the repository includes “Addendum” folders and command scripts (e.g., all_in_one.sh, upgrade scripts, ArgoCD configurations, and HAProxy and dashboard setups) that prepare the environment.
• Application Workloads: Several labs deploy sample applications such as Ghost, Apache, busybox, MySQL and others. These represent typical container applications that are used to test volume provisioning and performance.
Out Component Interactions
• How Trident communicates with the backend storage (e.g., ONTAP systems) and how it is used dynamically to provision, resize, or snapshot persistent volumes.
• When covering protection scenarios, include components like external monitoring/observability stacks (Prometheus, Grafana, Harvest) and GitOps tools (ArgoCD) that are integrated in some labs.
• For each lab scenario, annotate that there is a “scenario directory” that includes a set of YAML manifests, shell scripts, and configuration files that simulate a distinct environment workflow.
Architectural Patterns and Design Principles
• Modularity: The repository is segmented by Kubernetes version and further by “Scenarios” and “Addendum.” Each scenario is self-contained and has its own README file that explains the lab exercise.
• Extensibility: By including addendum folders and multiple versions, the project illustrates an evolutionary approach to lab design that supports testing upgrades, incorporating new features such as CSI snapshots, HAProxy configuration, and integration with GitOps tools.
• Infrastructure as Code: The vast collection of YAML files, shell scripts, and configuration files shows a strong emphasis on declarative configuration and automation in a lab environment.
Relevant Technologies, Frameworks, and Libraries
• Kubernetes – the container orchestration platform that is central to every lab.
• NetApp Trident – the CSI driver that integrates storage systems with Kubernetes.
• ONTAP (NAS/SAN) – the backend storage technology.
• CSI (Container Storage Interface) – the standard protocol between Kubernetes and storage drivers.
• Monitoring and DevOps tools such as Prometheus, Grafana, Harvest, ArgoCD, and even HAProxy which are part of some lab scenarios.
• Various sample applications (like Ghost, Apache, busybox) which serve as workload examples.
Additional Recommendations
• Flow “from the lab user’s terminal” (e.g., connecting via Putty to a host) to the control plane, which then triggers the lab scenario workflows.
• That the repository contains “scenario instructions” for each lab exercise, which are executed in dedicated directories.