[ceph-users] Re: Node Exporter keep failing while upgrading cluster in Air-gapped ( isolated environment ).

2024-07-16 Thread Adam King
I wouldn't worry about the one the config option gives you right now. The one on your local repo looks like the same version. For isolated deployments like this, the default options aren't going to work, as they'll always point to images that require internet access to pull. I'd just update the con

[ceph-users] Re: Node Exporter keep failing while upgrading cluster in Air-gapped ( isolated environment ).

2024-07-16 Thread Saif Mohammad
Hello Adam, Thanks for the prompt response. We have below image in private-registry for node-exporter. 192.168.1.10:5000/prometheus/node-exporter v1.5.0 0da6a335fe13 19 months ago 22.5MB But upon ceph upgrade, we are getting the mentioned image ( quay.io/prometheus/node-expo

[ceph-users] Re: Node Exporter keep failing while upgrading cluster in Air-gapped ( isolated environment ).

2024-07-15 Thread Adam King
To pull quay.io/prometheus/node-exporter:v1.5.0 the nodes would need access to the internet, yes. I don't fully understand the reason for > root@node-01:~# ceph config set mgr > mgr/cephadm/container_image_node_exporter > quay.io/prometheus/node-exporter:v1.5.0 though. Why not tell it to point t