(The best part is this probably violates the #GDPR)
It turns out that there is no way to disable the **OTHER** #analytics #spyware that @grafana adds to #Loki
Start by adding `grafana-agent-operator.agent.enableReporting: false` to the last post. By default it installs and sets up the "Grafana Agent" and that flag must have slipped their minds in the release notes where this mess is nominally "documented". (Not in the docs. In the old *release notes*.)
Doesn't matter. There is no way to add 'enableReporting: false' to the GrafanaAgent CR itself. (Yay for non-standardization of flags.)
The "more fun" on this #privacy pile is in the same spot. It requests a LOT of permissions that look more related to their needs than mine: https://github.com/grafana/loki/blob/main/production/helm/loki/templates/monitoring/grafana-agent.yaml#L50-L74
It wants to scrape EVERYTHING. It wants to scrape stuff that I skip because its too noisy. What possible reason could the logger have for scraping ingress & cadvisor?
#monitoring #prometheus #kubernetes #k8s #grafana #helmchart #telemetry
#gdpr #analytics #spyware #loki #privacy #monitoring #prometheus #kubernetes #k8s #grafana #helmchart #telemetry
Today's adventure in #darkpattern #surveillance comes from #Grafana #Loki. (Not a surprise, but this is why I run egress filters and dns #adblock in my #homelab clusters.)
I know not everyone agrees that #optout #telemetry is a dark pattern, but you might agree with me about this one after you see it documented:
> # -- Optional analytics configuration
> analytics: {}
Enlightening, isn't it? There are other empty blocks, but they are either fairly standard or are described elsewhere in the document.
If you are familiar with #helm, you won't despair because you have the power of `analytics.enabled: false`. That works on the rest of this chart and is the standard way to en/disable things.
It doesn't work that way.
Let me save you some time with the terrible new #github code search. Here is the actual syntax:
"analytics.reporting_enabled: false"
This was caught by #adguard and enforced by an egress #networkpolicy
#darkpattern #surveillance #grafana #loki #adblock #homelab #optout #telemetry #helm #github #adguard #networkpolicy #monitoring #prometheus #kubernetes #k3s #k8s #helmchart
What do you use to deploy helm charts? When I have everything in terraform I stick to it, but for personal use I didn't want to have one big codebase and statefiles. So I'm using #helmfile
#helmfile #blog #helm #helmchart
I created helm chart for Kanboard![1] It's simple for now, maybe it will get more features later.
If you don't know that is Kanboard take a look at their webpage [2] - I'm using it to track my personal tasks, especially recurring ones.
[1] https://github.com/11mariom/kanboard-helm-chart
[2] https://kanboard.org/