Using OVS internal interfaces instead of veth ?

[champtar]

Has anyone attempted to use OVS internal interfaces instead of veth ?
It was mentioned a long time ago by @phoracek in #2 (comment)_ but can't find anything about why it was never done (maybe some hard blocker)

BTW the documentation is misleading:

ovs-cni/docs/cni-plugin.md

Line 60 in 8a4f334

* `interface_type` (string, optional): type of the interface belongs to ports. if value is "", ovs will use default interface of type 'internal'

In my testing I have

# ovs-vsctl show
ffe87f74-4b6f-42f6-87b6-25504ab94ce3
    Bridge k8s-ovs
        Port k8s-ovs
            Interface k8s-ovs
                type: internal
        Port veth97d92a70
            Interface veth97d92a70
    ovs_version: "3.2.2"

[phoracek]

I have a vague recollection of it: The issue of internal interfaces was that they are created in the host network namespace and only then they can be moved to the pod's network namespace. I think that it was causing some noise, but I don't remember the details.

@wangyueyu64 hey! Not sure if you are still around, but if you are, any chance you could look into the interface_type documentation issue that @champtar has mentioned?