deckhouse VS agent

And while k3s sounds easy, it's not after even a slightly larger scale.

If one willing to have in-house k8s today I would recommend https://deckhouse.io/ (I'm not affiliated with them)

Deckhouse

Check Deckhouse as well (https://github.com/deckhouse/deckhouse). Cilium integration was added there recently.

Release Deckhouse v1.26.0 · deckhouse/deckhouse (github.com)

Consider Deckhouse as another option that can be installed everywhere: bare metal, private and public clouds. It has an Open Source core offered in Community Edition, but the pricing for Enterprise Edition is also a fit for small companies. All configuration is made via Custom Resources, all routines (like updating Kubernetes versions and related system components) are automated.

We use cert-manager in our K8s platform for years and it works perfectly. I don't think there is any chance today to compete with it in terms of community adoption. I also can't find any GitHub links for your project which is the most widely accepted way to become trusted by the community — simply because it covers all the basic needs everyone got used to (in the Open Source world): we can see how the code is developed, we can contribute to it, discuss the issues and concerns we have, etc.

We use Vector to ship logs to different storages (including Loki). You can even find the implementation here, however, I am not sure how useful it might be since it's quite specific (Golang hooks for addon-operator). Our manifests are available there as well.

And has an agent that can be run on the host to monitor it: https://github.com/grafana/agent

For example, there are things like https://github.com/grafana/agent

Hey, I would like to lint my agent config in vscode. Did someone know where I can find the agent config JSON schema ? I've searched on https://github.com/grafana/agent and https://grafana.com/docs/agent/latest/ but cant find anything like this ...

Grafana Agent can stream data back to you.

At the time, Jaeger did not support OTEL format, which meant we needed our telemetry collector to export spans in Jaeger format. We were able to push this small fix to add a Jaeger exporter on the Agent.

Furthermore, would recommend Grafana Agent OR Prometheus Agent in this case since you probably don't need the Prometheus UI in each Cluster as well as the Alerting stuff that is inside Prometheus. (Mimir will do the ruling stuff for you). Grafana Agent also has an Operator mode if you want to use ServiceMonitor and PodMonitor CustomResources.

There were a bunch of alternatives to solve this before, like grafana agent [0], vm agent [1] or opentelemetry collector [2].

[0] - https://github.com/grafana/agent

[1] - https://github.com/VictoriaMetrics/VictoriaMetrics/tree/mast...

[2] - https://github.com/open-telemetry/opentelemetry-collector

This might be a reasonable use case for the Grafana Agent. It's basically a Prometheus instance, but without the local storage. Just forwards the data.