gitchegumi/homelab
gitchegumi/homelab
Watch
1
0
Fork
You've already forked homelab
 0
Code Issues 1 Pull requests Projects 1 Wiki Activity Actions

Select and configure dynamic TrueNAS-backed Kubernetes storage #5

New issue
Closed
opened 2026-08-29 00:22:49 -05:00 by portegumi · 1 comment
portegumi commented 2026-08-29 00:22:49 -05:00
Collaborator
Copy link

Description

Choose a supported method for Kubernetes to provision persistent storage on TrueNAS while retaining TrueNAS as the storage appliance. The design must distinguish shared-file workloads from block/database workloads.

Scope

  • Evaluate the appropriate TrueNAS CSI, NFS, and iSCSI integration options.
  • Select dynamic provisioning paths for shared-file and block storage.
  • Define how TrueNAS API credentials or storage credentials will be supplied without entering the public repository.
  • Validate provisioning, attachment or mounting, expansion where supported, and deletion behavior.

Acceptance criteria

  • The selected dynamic storage approach and rationale are documented.
  • Shared-file and block/database use cases are explicitly distinguished.
  • A disposable dynamically provisioned volume survives pod recreation and passes read/write validation.
  • Reclaim behavior is tested and documented.
  • Credential handling uses an out-of-repository mechanism.

Dependencies / blockers

Requires a healthy cluster, network reachability to TrueNAS, and completion of the relevant TrueNAS access planning. No CSI implementation is predetermined by this issue.

## Description Choose a supported method for Kubernetes to provision persistent storage on TrueNAS while retaining TrueNAS as the storage appliance. The design must distinguish shared-file workloads from block/database workloads. ## Scope - Evaluate the appropriate TrueNAS CSI, NFS, and iSCSI integration options. - Select dynamic provisioning paths for shared-file and block storage. - Define how TrueNAS API credentials or storage credentials will be supplied without entering the public repository. - Validate provisioning, attachment or mounting, expansion where supported, and deletion behavior. ## Acceptance criteria - [x] The selected dynamic storage approach and rationale are documented. - [x] Shared-file and block/database use cases are explicitly distinguished. - [x] A disposable dynamically provisioned volume survives pod recreation and passes read/write validation. - [x] Reclaim behavior is tested and documented. - [x] Credential handling uses an out-of-repository mechanism. ## Dependencies / blockers Requires a healthy cluster, network reachability to TrueNAS, and completion of the relevant TrueNAS access planning. No CSI implementation is predetermined by this issue.
portegumi commented 2026-08-31 16:58:07 -05:00
Author
Collaborator
Copy link

Completion evidence:

  • TrueNAS CSI dynamically provisions both truenas-nfs RWX volumes and truenas-iscsi RWO volumes.
  • NFS and iSCSI test manifests are committed under k8s/storage/tests.
  • Disposable volumes reached Bound, passed read/write checks, and retained data through pod recreation.
  • Volume expansion and deletion/reclaim behavior were validated; disposable PVs and their TrueNAS backing storage were removed as expected.
  • CSI/API credentials are supplied through Kubernetes secrets and are not committed to the repository.

All acceptance criteria are complete.

Completion evidence: - TrueNAS CSI dynamically provisions both `truenas-nfs` RWX volumes and `truenas-iscsi` RWO volumes. - NFS and iSCSI test manifests are committed under [`k8s/storage/tests`](https://git.gitchegumi.com/gitchegumi/homelab/src/branch/main/k8s/storage/tests). - Disposable volumes reached `Bound`, passed read/write checks, and retained data through pod recreation. - Volume expansion and deletion/reclaim behavior were validated; disposable PVs and their TrueNAS backing storage were removed as expected. - CSI/API credentials are supplied through Kubernetes secrets and are not committed to the repository. All acceptance criteria are complete.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
app-migration
Migration of existing applications into Kubernetes

  
ci-cd
Forgejo Actions, runners, GitOps, and delivery automation

  
cluster
RKE2 cluster bootstrap and node lifecycle

  
Discussion
Use this label when the issue is meant to be a discussion. These items will not be actioned on, but may lead to new issues with action items.

  
documentation
Architecture, inventory, conventions, and runbooks

  
gpu
NVIDIA enablement and GPU workload scheduling

  
networking
Cluster networking, load balancing, addressing, and DNS

  
security
Security controls and secret-handling safeguards

  
storage
TrueNAS, CSI, NFS, iSCSI, and local persistent storage

  
uds
Defense Unicorns UDS prerequisites and deployment

No labels
app-migration
ci-cd
cluster
Discussion
documentation
gpu
networking
security
storage
uds
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Homelab k8s Setup
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#19 Design and build a self-service multi-tenant Foundry VTT hosting platform
gitchegumi/homelab
Reference
gitchegumi/homelab#5
No description provided.