docs: replace all remaining TrueNAS references with NASty

Complete renaming across docs, charts, scripts, and tests:
- charts: .Values.truenas.* → .Values.nasty.*, all templates updated
- scripts: cleanup-all-truenas-resources.sh → cleanup-all-nasty-resources.sh
- integration tests: TRUENAS_HOST/API_KEY/POOL → NASTY_HOST/API_KEY/POOL
- docs: QUICKSTART, DEPLOYMENT, FEATURES, ADOPTION, e2e README updated
- Delete COMPARISON-*.md docs (no longer relevant for NASty)
- CONTRIBUTING.md, SECURITY.md, sonar-project.properties updated
- dashboard, kind-config.yaml, deploy/README.md updated

Author: fenio

.github/workflows/qemu-e2e.yml

@@ -307,10 +307,10 @@ jobs:
             upgrade --install nasty-csi-driver ./charts/nasty-csi-driver
             --namespace kube-system
             --wait --timeout 8m
-            --set "truenas.url=wss://${NASTY_HOST}/api/current"
-            --set "truenas.apiKey=${NASTY_API_KEY}"
-            --set "truenas.pool=${NASTY_POOL}"
-            --set "truenas.skipTLSVerify=true"
+            --set "nasty.url=wss://${NASTY_HOST}/api/current"
+            --set "nasty.apiKey=${NASTY_API_KEY}"
+            --set "nasty.pool=${NASTY_POOL}"
+            --set "nasty.skipTLSVerify=true"
             --set "image.repository=ghcr.io/fenio/nasty-csi"
             --set "image.tag=qemu-test"
             --set "image.pullPolicy=Never"

.github/workflows/release.yml

@@ -111,7 +111,7 @@ jobs:
           helm template nasty-csi charts/nasty-csi-driver \
             --namespace kube-system \
             --set nasty.url="wss://NASTY_IP/api/current" \
-            --set truenas.apiKey="REPLACE_WITH_API_KEY" \
+            --set nasty.apiKey="REPLACE_WITH_API_KEY" \
             --set storageClasses[0].name=nasty-csi-nfs \
             --set storageClasses[0].enabled=true \
             --set storageClasses[0].protocol=nfs \

CONTRIBUTING.md

@@ -18,7 +18,7 @@ Before creating bug reports, please check existing issues to avoid duplicates. W
 - **Actual behavior** - What actually happened
 - **Environment details**:
   - Kubernetes version
-  - TrueNAS version
+  - NASty version
   - CSI driver version
   - Storage protocol (NFS/NVMe-oF)
 - **Logs** - Include relevant logs from controller and node pods
@@ -95,7 +95,7 @@ nasty-csi/
 │   └── nasty-csi-driver/    # Driver entry point
 ├── pkg/                    # Library code
 │   ├── driver/            # CSI driver implementation
-│   └── nastyapi/            # TrueNAS API client
+│   └── nastyapi/            # NASty API client
 ├── tests/                  # Test files
 │   ├── e2e/               # End-to-end tests
 │   └── integration/       # Integration tests
@@ -144,9 +144,9 @@ Integration tests use [Ginkgo](https://onsi.github.io/ginkgo/) and run automatic
 go install github.com/onsi/ginkgo/v2/ginkgo@latest
 
 # Set required environment variables
-export TRUENAS_HOST="your-truenas-ip"
-export TRUENAS_API_KEY="your-api-key"
-export TRUENAS_POOL="your-pool"
+export NASTY_HOST="your-nasty-ip"
+export NASTY_API_KEY="your-api-key"
+export NASTY_POOL="your-pool"
 
 # Run NFS E2E tests
 ginkgo -v --timeout=25m ./tests/e2e/nfs/...
@@ -203,7 +203,7 @@ feat: Add support for volume expansion in NVMe-oF
 
 fix: Correct NFS mount options for better performance
 
-docs: Update quickstart guide with TrueNAS 24.04 specifics
+docs: Update quickstart guide with NASty specifics
 
 test: Add integration tests for NVMe-oF volume lifecycle
 ```

Makefile

@@ -104,7 +104,7 @@ test-coverage:
 test-all: test-unit test-sanity
 	@echo "All tests completed"
 
-# E2E tests (requires Ginkgo CLI and TrueNAS connection)
+# E2E tests (requires Ginkgo CLI and NASty connection)
 test-e2e:
 	@echo "Running all E2E tests..."
 	ginkgo -v --timeout=60m ./tests/e2e/...

README.md

@@ -25,26 +25,26 @@ We will acknowledge your report within 48 hours and provide a timeline for a fix
 ### Credential Management
 
 **API Keys and Secrets:**
-- TrueNAS API keys are stored in Kubernetes Secrets
+- NASty API keys are stored in Kubernetes Secrets
 - Secrets should use RBAC to restrict access
 - Never commit credentials to git
 - Use `.local.yaml` files for local development (automatically ignored by git)
 
 **Best Practices:**
 - Use dedicated API keys with minimal required permissions
 - Rotate API keys regularly
-- Enable TrueNAS API audit logging
+- Enable NASty API audit logging
 - Monitor API key usage
 
 ### Network Security
 
 **TLS/SSL:**
-- Always use `wss://` (WebSocket Secure) for TrueNAS API connections
+- Always use `wss://` (WebSocket Secure) for NASty API connections
 - Verify TLS certificates in production
 - For self-signed certificates, understand the security implications
 
 **Network Isolation:**
-- Restrict network access to TrueNAS management interface
+- Restrict network access to NASty management interface
 - Use firewalls to limit access to storage ports:
   - NFS: TCP 2049
   - NVMe-oF: TCP 4420
@@ -53,7 +53,7 @@ We will acknowledge your report within 48 hours and provide a timeline for a fix
 **Self-Hosted Runners:**
 - Use private GitHub repositories to prevent malicious PR execution
 - Isolate runners on dedicated network segments
-- Use Wireguard VPN for secure communication with TrueNAS
+- Use Wireguard VPN for secure communication with NASty
 - Regularly update runner systems and dependencies
 
 ### Kubernetes Security
@@ -71,24 +71,24 @@ We will acknowledge your report within 48 hours and provide a timeline for a fix
 **Secrets:**
 ```bash
 # Create secret with proper permissions
-kubectl create secret generic truenas-csi-secret \
+kubectl create secret generic nasty-csi-secret \
   --from-literal=api-key=YOUR_API_KEY \
-  --from-literal=api-url=wss://YOUR-TRUENAS-IP:443/api/current \
+  --from-literal=api-url=wss://YOUR-NASTY-IP:443/api/current \
   --namespace kube-system
 
 # Restrict access
 kubectl create role secret-reader \
   --verb=get \
   --resource=secrets \
-  --resource-name=truenas-csi-secret \
+  --resource-name=nasty-csi-secret \
   --namespace kube-system
 ```
 
 ### Data Security
 
 **Volume Data:**
-- Data in volumes is subject to TrueNAS permissions and encryption
-- Use TrueNAS dataset encryption for sensitive data
+- Data in volumes is subject to NASty permissions and encryption
+- Use NASty dataset encryption for sensitive data
 - Implement backup strategies
 - Consider volume encryption at application level for additional security
 
@@ -120,8 +120,8 @@ kubectl create role secret-reader \
   kubectl logs -n kube-system -l app.kubernetes.io/name=nasty-csi-driver
   ```
 
-**TrueNAS Audit:**
-- Enable TrueNAS API audit logging
+**NASty Audit:**
+- Enable NASty API audit logging
 - Review logs for unauthorized access attempts
 - Monitor dataset access patterns
 
@@ -169,4 +169,4 @@ This driver does not currently undergo formal security audits or compliance cert
 
 - [Kubernetes Secrets Management](https://kubernetes.io/docs/concepts/configuration/secret/)
 - [CSI Driver Security Considerations](https://kubernetes-csi.github.io/docs/)
-- [TrueNAS Security Best Practices](https://www.truenas.com/docs/)
+- 

SECURITY.md

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: nasty-csi-driver
-description: A Helm chart for TrueNAS Scale CSI Driver - providing NFS, NVMe-oF, and iSCSI storage for Kubernetes (requires TrueNAS Scale 25.10+)
+description: A Helm chart for NASty CSI Driver - providing NFS, NVMe-oF, and iSCSI storage for Kubernetes
 
 # A chart can be either an 'application' or a 'library' chart.
 type: application
@@ -17,7 +17,7 @@ appVersion: "v0.17.3"
 keywords:
   - storage
   - csi
-  - truenas
+  - nasty
   - nfs
   - nvmeof
   - iscsi
@@ -31,4 +31,4 @@ maintainers:
     email: fenio@debian.org
     url: https://github.com/fenio
 
-icon: https://www.truenas.com/wp-content/uploads/2023/01/TrueNAS_Open_Storage.png
+icon: https://github.com/nasty-project/nasty-csi/raw/main/docs/nasty-logo.png