Error: Not authenticated in Browser when trying with http://external_ip:nodeport

[nigoyal7 (Nitin Goyal)]

yes, i have added the certificate to trust-store

Thanks
Nitin Goyal

[davidwayne]

Can you disable the cluster collector connection in your rule and try just with the kubernetes API and see if the error is still the same ?

[nigoyal7 (Nitin Goyal)]

Hi David,

I have tried disabling cluster collector in kubernetes rules, used kubernetes API IP and port, still getting same error as shown in screenshot below…

I have also tried disabling and enabling SSL certificate verification, its giving same error in both ways…

Thanks
Nitin Goyal

[chauhan_sudhir]

The error message. looks like no data on that endpoint. How about executing it from the command line with --debug and --verbose ?

If I execute it from my command line on our test on-prem cluster on 1.21, it looks like this:

$ kubectl get --raw /api/v1/nodes/k8-w1/proxy/healthz -v=9
I0602 08:10:34.950619 3643313 loader.go:372] Config loaded from file: /root/.kube/config
I0602 08:10:34.951341 3643313 round_trippers.go:435] curl -k -v -XGET -H “Accept: application/json, /” -H “User-Agent: kubectl/v1.21.7 (linux/amd64) kubernetes/1f86634” ‘https://1.2.3.4:6443/api/v1/nodes/k8-w1/proxy/healthz’
I0602 08:10:34.983233 3643313 round_trippers.go:454] GET https://1.2.3.4:6443/api/v1/nodes/k8-w1/proxy/healthz 200 OK in 31 milliseconds
I0602 08:10:34.983257 3643313 round_trippers.go:460] Response Headers:
I0602 08:10:34.983267 3643313 round_trippers.go:463] Content-Type: text/plain; charset=utf-8
I0602 08:10:34.983271 3643313 round_trippers.go:463] Date: Thu, 02 Jun 2022 06:10:34 GMT
I0602 08:10:34.983274 3643313 round_trippers.go:463] X-Content-Type-Options: nosniff
I0602 08:10:34.983276 3643313 round_trippers.go:463] Content-Length: 2
I0602 08:10:34.983279 3643313 round_trippers.go:463] Cache-Control: no-cache, private

[nigoyal7 (Nitin Goyal)]

Hi Sudhir,

I am able to get metrics with below kubernetes rule…thankyou for your help in this issue…

Further i am getting below two issues while getting metrics in checkmk application:

Issue1:
When any one or more than one worker node is down, checkmk does not provide metrics from other nodes which are in ready state and gives below error, here worker-2 instance is stopped

Issue2:
When all worker nodes are up and running, metrics,
Under hosts we are getting pods, deployments, nodes state of only hosts like master, worker also host count includes pods, deployments as well which should only provide nodes count…

Below is piggyback configuration:

Please help to solve metrics issue…thankyou

Thanks & Regards,
Nitin Goyal

[nigoyal7 (Nitin Goyal)]

Hi Team,

Can you please help to solve above two issues…

Thanks
Nitin Goyal

[davidwayne]

ssue2:
When all worker nodes are up and running, metrics,
Under hosts we are getting pods, deployments, nodes state of only hosts like master, worker also host count includes pods, deployments as well which should only provide nodes count…

This is not clearly described. What do you want to achieve here?

[davidwayne]

@nigoyal7

Issue1:
When any one or more than one worker node is down, checkmk does not provide metrics from other nodes which are in ready state and gives below error, here worker-2 instance is stopped

Workker-2 instance is stopped means it shows NotReady under “kubectl get nodes” for this worker node. Correct ? If yes, I can’t reproduce it.