snmp_exporter VS charts

It is kind of described here:https://github.com/prometheus/snmp_exporter/issues/405

The SNMP exporter can do lookups. Take a look at this documentation.

wget https://github.com/prometheus/snmp_exporter/releases/download/v0.21.0/snmp_exporter-0.21.0.linux-amd64.tar.gz

You need to find the OSBs for the router, and add those to the explorer. Take a look at this doc: https://github.com/prometheus/snmp_exporter/blob/main/generator/README.md

You can fetch this metrics using the SNMP exporter https://github.com/prometheus/snmp_exporter

As a maintainer of the Prometheus SNMP exporter, and the defacto standard implementation of SNMP in Go, I can tell you exactly how convoluted SNMP is at a protocol and specification level.

Refer to https://github.com/prometheus/snmp_exporter and https://blog.paessler.com/how-to-enable-snmp-on-your-operating-system

For example, you can use unpoller to bring your unifi stuff into the same system as your SNMP data.

SNMP by itself is a rather crude protocol, with values being identified as OID (Object IDs). Those are numerical identifiers. A MIB-File contains the information on how to translate these OIDs into workable data. There is some information on how to feed these files to the exporter located here: https://github.com/prometheus/snmp_exporter/tree/main/generator

Source: I help maintain open source SNMP libraries and SNMP pollers.

Spinning up workloads in kubernetes is much different than just spinning up a container in docker or even with docker compose. If someone has not already packaged it in a helm chart or some other kubernetes workload you'll have to develop one yourself. There are some nice library charts you can use as a base that should handle just about any random docker image you want to deploy. https://github.com/bjw-s/helm-charts/tree/main/charts/library/common there is also a repo of pre developed charts for common images. https://github.com/k8s-at-home/charts but be aware it was recently deprecated so it won't be receiving any updates.

Take a look at https://github.com/k8s-at-home/charts (recently deprecated but still a fantastic resource) - there are charts for the popular Arrs , tools, etc. You could deploy each chart individually into a namespace, or you could create yourself an "umbrella" chart which pulls in all the necessary charts as dependencies.

Library charts. A very thorough example can be seen here and usages of it here.

Could it be related to this? https://github.com/k8s-at-home/charts/pull/1435/files

I'd submitted a helm chart at https://github.com/k8s-at-home/charts/tree/master/charts/stable/firefly-iii if you want to try out

I know /u/stefantigro means well but the way you are both doing the helm charts is not ideal, helm charts are meant to be shared, not as a means to install apps into your cluster from a local folder. While they can be, it's not a good pattern. Take the helm chart from here for example. This is a published helm chart you can install using the commands in the Readme and you only need to provide the configuration for your instance from the values.yaml file. You can take a look at the values I use for this helm chart here. You can also see I'm using an custom Sonarr image, this image is tailored to running in Kubernetes

There is a working Helm chart for k8s-at-home that should be a good starting point. The biggest hurdle I see is that homebridge can conflict with SCALE's mDNS service as seen in this linked post.

There's an actual helm chart published here.