Should we move kindnet assets from downstream?

[pmtk]

We recently moved assets for topolvm upstream. In the same spirit, should we also move kindnet assets?

See assets/manifests and look for kindnet in the downstream .spec file.

@praveenkumar I think your opinion is most important right now as the downstream projects you're maintaining are making use of the kindnet.

[praveenkumar]

Thank you for adding me to the discussion. I think as long as I can build the microshift rpm which by default disable the ovn-k and enable the kindnet, should be good enough for minc (microshift in container usecase).

FYI it will not only the kindnet but also kube-proxy need to be move because kindnet is depend on it but ovn-k is not depend on it.

[pmtk]

That's the goal, piggy back on existing downstream .spec with some additions (topolvm rpm integration with microshift rpm) and replacements (OCP -> OKD images)

[ggiguash]

Looks like there's an agreement here. I'm converting the discussion to an issue.