Hi all.
I’m running Prometheus as a app…
it however seems to refer to the internal resolve.conf that basically just points back at itself, also not allowing me to edit this file.
My TN is set to resolve to my pfSense.
G
Is it only the Prometheus App that has the problem?
Which version of SCALE?
You didn’t pass it a config file?
The config file location is specified in the github note
Hi,
From what I can figure out it pulls in a setting thats set for the K8S cluster… and well if you try and change that it has a note saying the cluster will be recreated and all apps lost, which is not a option.
If I try and change the value in the container it tells me it’s read only. If you do a df -k it looks like it’s mounted in… but if I go look at the mount source there is no resolve.conf there.
Scale: Dragonfish-24.04.1. So far it’s only the Prometheus environment that needs to be able to get to my DNS… Prometheus when it scrapes end points use the target name/ip given to store the data points against. which in a very small environment is ok… we know the hosts for those ip’s, but a better solution is to point it to the dns entry, thus the points are then stored per host name. Allot more user friendly.
I configure prometheus via the prometheus.yml and this is where the problem starts, using hostnames it can’t find the target due to resolve.conf wrong…
G
If its important, I’d try 24.10
The developers are active in that version and it may have already been fixed.
I’m waiting for a replacement hdd for my main disk pool. as soon as thats in and resilvered will then do the upgrade. hoping it’s fixed in EE, move off K8S.
G