# Migration help from k8s INC to F5 NIC

**URL:** <https://community.nginx.org/t/migration-help-from-k8s-inc-to-f5-nic/9488>\
**Category:** ingress-nginx Migration Help\
**Created:** [May 14, 2026, 9:41am UTC](https://community.nginx.org/t/migration-help-from-k8s-inc-to-f5-nic/9488 "2026-05-14T09:41:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![parallel\_stories](https://drob5swvtjqxg.cloudfront.net/user_avatar/community.nginx.org/parallel_stories/32/4056_2.png) [@parallel\_stories](https://community.nginx.org/u/parallel_stories)\
**Post date:** [May 14, 2026, 9:41am UTC](https://community.nginx.org/t/migration-help-from-k8s-inc-to-f5-nic/9488/1 "2026-05-14T09:41:34Z")

</div>

> [@Need migration help for following ingress from k8s INC to F5 NIC](https://community.nginx.org/t/need-migration-help-for-following-ingress-from-k8s-inc-to-f5-nic/9483):
>
> Please use this template for troubleshooting questions. My issue: We need help in converting this ingress from k8s INC to F5 NIC with best way possible. Preferably sticking to ingress yaml only for easier migration. Only go to additional CRDs if needed. \*\*How I encountered the problem: We are getting 404 for the following instead of 200. The ingress we were using for k8s INC: \*\* apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: myapp-ingress namespace: myapp annotations: …