Skip to content

fix(logging): drop longhorn storageClassName on fluentd PVC #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Varashi merged 1 commit into from
May 27, 2026
Merged

fix(logging): drop longhorn storageClassName on fluentd PVC #154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions cluster-talos/kubernetes/infrastructure/platform/logging/logging-config/app/logging.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,16 +65,16 @@ spec:
# File-buffer on a small PVC per replica — survives pod restart,
# absorbs vcflogs back-pressure. PVC size chosen to hold ~1h of
# peak log volume (LogVerbose=1 on prod plex can push 200MB/h).
# storageClassName omitted on purpose → cluster default (vsan,
# vSphere CSI). Longhorn was removed earlier; vsan handles
# ReadWriteOnce + WaitForFirstConsumer just fine.
bufferStorageVolume:
pvc:
spec:
accessModes: [ReadWriteOnce]
resources:
requests:
storage: 5Gi
# k8s-talos default StorageClass is longhorn — change here
# if/when we migrate (memory: longhorn removal planned).
storageClassName: longhorn
# Tolerate all nodes so the aggregator can land anywhere if
# capacity tightens.
tolerations:
Expand Down
Loading