Add liveliness probe for openshift sync pod

Solution Unverified - Updated -

Issue

  • Sync pod failed to update node.openshift.io/md5sum or stop updating. Many times multiple nodes label were wrong while sync pods still running on those nodes. Restart sync pod solve the problem.
  • It will be helpful to add liveliness probe to sync pod as it a very critical part of the platform. If any node in cluster doesn't have a valid md5sum, scale up playbook fails.
  • what liveliness probe should do is check if md5sum of node-config.yml is equal to node's node.openshift.io/md5sum.

Environment

  • OpenShift Container Platform
    • 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content