Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using OVS internal interfaces instead of veth ? #294

Open
champtar opened this issue Nov 20, 2023 · 0 comments
Open

Using OVS internal interfaces instead of veth ? #294

champtar opened this issue Nov 20, 2023 · 0 comments

Comments

@champtar
Copy link

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:

* `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"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant