Build OVN version of bootc image

[randomlygeneratedname1]

Hi

Would it be possible to also have OVN version in your bootc builds and future bootc ISO builds?

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Add support for OVN-K images in OKD builds for ARM architecture #123
• Build an ISO for each bootc image under releases #178
• Include OLM operator into the bootc image #182

👤 Suggested Assignees

• randomlygeneratedname1
• ggiguash

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[ggiguash]

This is currently blocked on #123 because we have no OVN for aarch64 platform.

[ggiguash]

@randomlygeneratedname1 , can you share what OVN feature your require that's missing in the Kindnet CNI?

[randomlygeneratedname1]

I might be mistaken, but I thought kind was meant for dev/testing/lab environments inside Docker or Podman containers? I don't know if OpenShift routes are supported with kindnet, but that's something I require. I'm just more familiar with OVN coming from OpenShift during daytime. And unless kindnet is much less resource heavy, I see a benefit in using the same as regular OKD/OpenShift. Also less differences if you are deploying or troubleshooting something that you only find OKD/OpenShift examples on.

[ggiguash]

The main reason for using Kindnet is because it does not require a Linux kernel driver.
So, container images can also run on Windows for example.

Anyway, we need to build OVN images on both platforms, so this issue is totally valid.

[pmtk]

Hey @randomlygeneratedname1
I performed a smoke test and routes seem to work with kindnet just fine. Is you preference for OVN-K strictly due to wanting a "same but no pull secret" env for playing around?

[randomlygeneratedname1]

@pmtk, I actually tested routes myself yesterday, and found out that it works.

Yes, my preference is to have as close to how I would deploy a production environment as possible when I lab at home and for my self-hosting. That way most of knowledge I gain is transferable to work (and the other way around), but also to keep my self-hosted services as secure and stable as possible, without needing to pull authenticated from Red Hat. At work I use the Red Hat versions of software for even more stability and support.