OpenShift cluster network operator may crash during a cluster version update.

OpenShift version 4.14 and later    

Issue is not easy to reproduce during a normal and successful version update.

Start an OpenShift patch version update. Once the first Kubernetes API server pod has been started on the new version, the cluster feature gate status will only have the new version. Restart the OpenShift network operator pod and it will crash with an error similar to the following:

E0429 19:36:24.460120       1 simple_featuregate_reader.go:290] cluster failed with : unable to determine features: missing desired version "4.14.16" in featuregates.config.openshift.io/cluster
W0429 19:36:43.501889       1 builder.go:109] graceful termination failed, controllers failed with error: failed to add controllers to manager: timed out waiting for FeatureGate detection

OpenShift cluster network operator pod may crash if there's a feature gate version mismatch.

OpenShift cluster network operator pod won't crash.

See https://ibm-argonauts.slack.com/archives/C01C8502FMM/p1714551198353339 for more information and initial discussion.