-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
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
Does this not support monitoring of node ? #324
Comments
I want to monitor node when Node Condition is ready but status is false. |
@abahmed Any idea ? |
Thank you @amandpay for raising this |
Hi @abahmed any specific timeline for this ? |
@amandpay will work on it ASAP and it's expected to be landed within one week from now |
Thanks @abahmed. |
@abahmed Today i observed , i had a pod with termination grace period 60 sec and a sleep with PreStop of 30 secs , so pod was in terminating state for 30 secs due to sleep , i got alert for this {This message is too long to display here. Please visit the external source app to view the message.} |
Hey @abahmed , any update on this ? |
@abahmed Is this working , my node was in NotReady state for 5 mins as kubelet was not running but no alerts receive ? |
@amandpay Can you share logs of kwatch? |
Hi @abahmed , any updates here |
My rbac files lookes like below:
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: {{ .Release.Name }}
rules:
resources: ["pods", "pods/log", "events", "nodes"]
verbs: ["get", "watch", "list"]
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: {{ .Release.Name }}
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: {{ .Release.Name }}
subjects:
name: {{ .Release.Name }}
namespace: {{ .Release.Namespace }}
But one of node was Ready,SchedulingDisabled , but no alert fired. Is this expected or need some other configuration ?
The text was updated successfully, but these errors were encountered: