We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello everyone, I followed this instruction - https://github.com/kubernetes/node-problem-detector/blob/4ad49bbd84b8ced45ac825eac01ec93d9235935e/config/custom-plugin-monitor.json
and created a simple check which connects to kube api, fetches kube svc ip and tries to connect to it -
#!/bin/sh set -e export KUBECONFIG=/etc/kubernetes/kubelet.conf kube_svc=$(kubectl get svc kubernetes -o jsonpath="{.spec.clusterIP}") curl --cacert /etc/kubernetes/pki/ca.crt https://${kube_svc}
It's mounted using config map
NPD returns this -
I0928 06:09:24.090884 1 plugin.go:281] Start logs from plugin {Type:NPD Condition: Reason:KubeServiceDown Path:/scripts/kube_service.sh Args:[] TimeoutString:0xc000b0ae20 Timeout:5s} /scripts/kube_service.sh: 4: kubectl: not found
How are all those scripts supposed to get run if npd, obviously, doesn't have any binaries. Attach an extra container with kubectl?
Thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello everyone,
I followed this instruction - https://github.com/kubernetes/node-problem-detector/blob/4ad49bbd84b8ced45ac825eac01ec93d9235935e/config/custom-plugin-monitor.json
and created a simple check which connects to kube api, fetches kube svc ip and tries to connect to it -
It's mounted using config map
NPD returns this -
How are all those scripts supposed to get run if npd, obviously, doesn't have any binaries. Attach an extra container with kubectl?
Thanks
The text was updated successfully, but these errors were encountered: