rcourtman 9cfcdbb247 fix: Use per-node shared flag for storage deduplication ...

The storage deduplication logic only checked cluster config's Shared
flag, but this required the cluster config API call to succeed. When
the per-node storage API already returns shared=1 (as the user
verified), we should use that directly.

Now we check three sources for shared storage detection:
1. Per-node API shared flag (storage.Shared)
2. Cluster config shared flag (if available)
3. Storage type heuristics (NFS, RBD, PBS, etc.)

Related to #1049

2026-01-07 10:16:23 +00:00

..

ADAPTIVE_POLLING_ROLLOUT.md

feat: add --kube-include-all-deployments flag for Kubernetes agent

2025-12-18 20:58:30 +00:00

AUDIT_LOG_ROTATION.md

feat: add --kube-include-all-deployments flag for Kubernetes agent

2025-12-18 20:58:30 +00:00

AUTO_UPDATE.md

fix: Use per-node shared flag for storage deduplication

2026-01-07 10:16:23 +00:00

SENSOR_PROXY_CONFIG.md

feat: add --kube-include-all-deployments flag for Kubernetes agent

2025-12-18 20:58:30 +00:00

SENSOR_PROXY_LOGS.md

feat: add --kube-include-all-deployments flag for Kubernetes agent

2025-12-18 20:58:30 +00:00