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

Port trusted VIF moved to a Neutron extension #2172

Open
EmilienM opened this issue Sep 10, 2024 · 0 comments
Open

Port trusted VIF moved to a Neutron extension #2172

EmilienM opened this issue Sep 10, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@EmilienM
Copy link
Contributor

/kind bug

In recent Neutron, setting trusted key directly in the port's binding:profile has been deprecated and will be forbidden in future releases.
Dedicated port's attribute trusted, added by the API extension port_trusted_vif should be used instead.

New ML2 plugin extension port_trusted is now available. This extension implements the port_trusted_vif API extension which adds to the port resource a new boolean field called trusted.
This field should be used by admin users to set the port as trusted what was previously possible only through the port's
binding:profile dictionary.

With this extension enabled, it is now possible for admin users to set port as trusted without modifying directly 'binding:profile' field which is supposed to be just for machine to machine communication.

Source: https://review.opendev.org/c/openstack/neutron/+/926068

We need to adapt CAPO with this change bu checking if the extension is enabled.

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
Status: Inbox
Development

No branches or pull requests

2 participants