fix(storage): consolidate longhorn-kafka → unified longhorn StorageClass
Removes duplicate longhorn-kafka StorageClass managed by Kafka chart. All applications now use single 'longhorn' StorageClass (3 replicas, Immediate binding). Changes: - Kafka chart: use 'longhorn' instead of 'longhorn-kafka' - Delete Kafka StorageClass template (no longer needed) - Update longhorn-storageclass.yaml to match deployed config (Immediate, not WaitForFirstConsumer) Existing Kafka PVCs remain bound to old longhorn-kafka StorageClass (safe - no data loss). New PVCs will use unified 'longhorn' StorageClass.
This commit is contained in:
@@ -7,8 +7,8 @@ kafkaCluster:
|
||||
nodePool:
|
||||
replicas: 3
|
||||
storage:
|
||||
# longhorn-kafka now uses numberOfReplicas: 3 across 3 zone-labeled nodes.
|
||||
class: longhorn-kafka
|
||||
# Use unified longhorn StorageClass (3 replicas, Immediate binding)
|
||||
class: longhorn
|
||||
# Per-node headroom: with 3 nodes and existing PVCs, estimate ~100+ Gi total
|
||||
# available. Each node hosts one replica of all 3 broker volumes, so 3 *
|
||||
# sizeGi must fit. Monitor usage during Kafka deployment.
|
||||
|
||||
Reference in New Issue
Block a user