Repository navigation
feat(openebs): make the Loki/MinIO/Alloy observability stack toggleable - #155
Merged
Merged
Conversation
The openebs chart ships an observability stack enabled by default: a Loki
StatefulSet, the MinIO StatefulSet backing it, an Alloy DaemonSet, and two extra
StorageClasses (openebs-loki-localpv, openebs-minio-localpv). The localpv
profile disabled the lvm/zfs/mayastor engines but left all of that on, so every
consumer of this helmfile got seven pods of logging nobody asked for.
On a small cluster it is worse than unnecessary. The Loki StatefulSet wants
three replicas with pod anti-affinity, so on a 1+2 kind cluster the two workers
take replicas 1 and 2, the control-plane node is tainted, and replica 0 sits
Pending forever — a permanently non-Running pod that has to be explained to
everyone who looks at the cluster. Seen on the u26-kind3 machinery cluster.
Both toggles default to TRUE, so this changes nothing for anyone today. That is
deliberate: this helmfile is consumed unpinned (`git::...helm.git`, no ref), so
a default flip would reach every cluster on its next apply rather than when
someone chose it.
Turn off with:
helmfile apply -f infra/openebs.yaml.gotmpl \
--state-values-set openebs_loki_enabled=false,openebs_alloy_enabled=false
MinIO has no toggle of its own — it is Loki's object store and a sub-dependency,
so loki.enabled=false is what removes it. openebs-hostpath, the StorageClass the
fleet actually uses, is unaffected by either toggle; verified by rendering the
helmfile both ways.
patrick-hermann-sva
temporarily deployed
to
k8s
August 11, 2026 13:46 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
patrick-hermann-sva
temporarily deployed
to
k8s
August 11, 2026 13:46 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
patrick-hermann-sva
added a commit
to stuttgart-things/ansible
that referenced
this pull request
Aug 11, 2026
…y clusters The openebs chart ships an observability stack enabled by default: a Loki StatefulSet, the MinIO StatefulSet backing it, an Alloy DaemonSet, and two extra StorageClasses. The localpv profile this play uses disabled the lvm/zfs/mayastor engines but left all of that on, so every machinery cluster ran seven pods of logging nobody asked for. On a 1+2 kind cluster — which is what every machinery cluster is — it cannot even run. Loki asks for three replicas with pod anti-affinity: the two workers take replicas 1 and 2, the control-plane node is tainted, and replica 0 sits Pending forever. u26-kind3 carried that permanently non-Running pod from the day it was built, and kind1 has the same one. MinIO has no toggle of its own — it is Loki's object store and a sub-dependency, so loki.enabled=false is what removes it. Alloy goes too, since a log shipper with no Loki ships logs at nothing. openebs-hostpath, the StorageClass everything here actually uses, is untouched. To pass the toggles, pre_crossplane_helmfiles entries become dicts with an optional state_values map rendered into --state-values-set. A plain string still works, so a caller overriding the list is unaffected. Requires stuttgart-things/helm#155, which adds the state values (defaulting to true there, so nothing else changes). Against an older helmfile the flags are simply ignored and the stack stays up. Verified on u26-kind3: after the run the openebs namespace holds only openebs-localpv-provisioner, the StorageClass list is down to openebs-hostpath, and the cluster has no non-Running pod left. The three MinIO StatefulSet PVCs survive a Helm removal and were deleted separately.
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The openebs chart ships an observability stack enabled by default: a Loki StatefulSet, the MinIO StatefulSet backing it, an Alloy DaemonSet, and two extra StorageClasses (
openebs-loki-localpv,openebs-minio-localpv). Thelocalpvprofile disabled the lvm/zfs/mayastor engines but left all of that on, so every consumer of this helmfile got seven pods of logging nobody asked for.On a small cluster it is worse than unnecessary: the Loki StatefulSet wants three replicas with pod anti-affinity, so on a 1+2 kind cluster the two workers take replicas 1 and 2, the control-plane node is tainted, and replica 0 sits
Pendingforever — a permanently non-Running pod that has to be explained to everyone who looks at the cluster. Seen building the u26-kind3 machinery cluster.Both toggles default to
trueDeliberately — this changes nothing for anyone today. This helmfile is consumed unpinned (
git::...helm.git, no ref), so flipping a default would reach every cluster on its next apply rather than when someone chose it.Notes
loki.enabled=falseis what removes it.openebs-hostpathis unaffected by either toggle — verified by rendering the helmfile both ways.🤖 Generated with Claude Code
https://claude.ai/code/session_01FSYX5dsdVdzLCuB6xYhaLK