etcd triggering and rolling out revision when etcd Cluster is degraded/unhealthy in OpenShift Container Platform 4

Solution Unverified - Updated -

Issue

  • On a cluster running with one degraded master, we started the masters recovery procedure, during which we delete the degraded node. Once the node is deleted, an etcd revision is started leaving the cluster with only one etcd pod running at some point in time, causing an API unavailability.
  • etcd triggering and rolling out revision when etcd Cluster is degraded/unhealthy in OpenShift Container Platform 4

Environment

  • Red Hat OpenShift Container Platform 4

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