Issues with frr-k8s and EgressService on Red Hat OpenShift 4.18

Solution Verified - Updated -

Issue

  • Frr-k8s pod goes into Crashloopbackoff state after the cluster upgrade to OpenShift 4.18.

  • When accessing external resource from a pod backed by the EgressService it doesn't uses IP address of the loadbalancer service.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.18

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