Kubernetes collector restarts and shows liveness check failures

Products

• CloudHealth

Issue/Introduction

Liveness check failures, API timeouts, and restarts may be due to the NAT instance schedule.

Resolution

If you use NAT instance instead of NAT gateway for Kubernetes, then be sure to review the NAT instance schedule. It's possible that this the NAT instance has powered off and severed the Kubernetes node internet connection, leading to liveness check failures and other API timeouts visible within logs.