f995680e2a
kube_node_status_ready and up metrics are obsolete to check the kubernetes node condition. When a kubelet is down that means node itself in NotReady state. With 1.3.1 kube-state-metrics exporter kube_node_status_condition metric provides the status value of the kubelet (essentially node). https://github.com/kubernetes/kube-state-metrics/blob/master/Documentation /node-metrics.md kube_node_status_condition includes condition=Ready and status as true, flase and unknown. When a kubelet is stopped the status will be unknown since the kubelet itself will unable to talk to API. In other cases it will be false. When the node is registered and available it will be set to true. Replaced the kube_node_status_ready with kube_node_status_condition and changed the 1h to 1m and increased the severity to "critical". Also modified the K8SKubeletDown definitions with 1m and critical sevrity Implements: Bug 1797133 Closes-Bug: #1797133 Change-Id: I025adb13c9d8642a218dfda1ff30f1577fa8c826 Signed-off-by: Kranthi Kiran Guttikonda <kranthi.guttikonda@b-yond.com>
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-5 on freenode
- Meeting Agenda Items: Agenda
Launchpad
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.