Skip to content

fix(logging): enableRecreateWorkloadOnImmutableFieldChange #155

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): enableRecreateWorkloadOnImmutableFieldChange #155

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
10 changes: 10 additions & 0 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 @@ -15,6 +15,16 @@ metadata:
namespace: logging
spec:
controlNamespace: logging
# Allow the operator to delete+recreate the Fluent Bit DS / Fluentd
# STS when an immutable spec field changes (e.g. PVC template's
# storageClassName, hostPath path, volume size). Without this, the
# operator refuses with "Object has to be recreated, but refusing
# to remove without explicitly being told so." For a homelab
# where the fluentd buffer is a few minutes of log replay, the
# data-loss-on-recreate cost is acceptable; for production
# deployments with strict log durability requirements, leave this
# false and use a planned manual sts delete + PVC migration.
enableRecreateWorkloadOnImmutableFieldChange: true

# ---------- Fluent Bit (per-node collector DaemonSet) ----------
fluentbit:
Expand Down
Loading