The below static pod failure event is seen at times for ipsec upgrade CI run at the time of cluster installation.

static pod lifecycle failure - static pod: "etcd" in namespace: "openshift-etcd" for revision: 8 on node: "ip-10-0-90-114.us-east-2.compute.internal" didn't show up, waited: 3m0s 

Example CI run: 
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/63667/rehearse-63667-periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-ipsec-upgrade/1929819282657513472

See slack discussion done so far for this run:

https://redhat-internal.slack.com/archives/C01CQA76KMX/p1749025739467429?thread_ts=1739374600.234989&cid=C01CQA76KMX

It must be triaged further by node team why static etc pod with particular revision 8 takes more time to come up on this particular node ip-10-0-90-114.us-east-2.compute.internal whereas in other control plane nodes this problem is not shown up.

We found it doesn't need an involvement of multus and ovnk to get this host networked pod up and running also not an IPsec related issue.

    1.
    2.
    3.