Update network binding plugins documentation to reflect GA status #926
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kubevirt-bot
added
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
aburdenthehand
changed the title
kubevirt-bot
removed
the
do-not-merge/work-in-progress
aburdenthehand
added
the
do-not-merge/work-in-progress
aburdenthehand
force-pushed
the
feature-lifecycle-updates-network
branch
from
5237333 to
4da45da
Compare
kubevirt-bot
removed
the
do-not-merge/work-in-progress
aburdenthehand
commented
Sep 16, 2025
| @@ -1,5 +1,5 @@ | |||
| # Network Binding Plugins | |||
| [v1.4.0, Beta feature] | |||
| [v1.5.0, GA feature] | |||
There was a problem hiding this comment.
Maybe we could just remove this altogether.
Comment on lines
19
to
20
| > **Note**: The network binding plugin infrastructure is GA as of v1.5.0. | ||
| > The SLIRP plugin is stable for production use. |
There was a problem hiding this comment.
Redundant; covered below under feature gates.
Comment on lines
37
to
38
| > **Note**: As of v1.5.0, the Network Binding Plugin feature is GA and enabled by default. | ||
| > No feature gate activation is required. |
There was a problem hiding this comment.
Suggested change
| > **Note**: As of v1.5.0, the Network Binding Plugin feature is GA and enabled by default. | |
| > No feature gate activation is required. | |
| As of v1.5.0, the Network Binding Plugin feature enabled by default and has no feature gate. | |
| The slirp plugin similarly has no feature gate of its own, but the plugin needs to be made available in the cluster by [registering it](./#slirp-registration). |
Comment on lines
40
to
41
| > **Note**: The specific slirp plugin has no feature gate of its own. It is up to the cluster | ||
| > admin to decide if the plugin is to be available in the cluster by registering it. |
There was a problem hiding this comment.
If the previous suggestion looks good, remove this.
Comment on lines
124
to
125
| > **Note**: As of v1.5.0, the Network Binding Plugin feature is GA and enabled by default. | ||
| > No feature gate activation is required. |
There was a problem hiding this comment.
Suggested change
| > **Note**: As of v1.5.0, the Network Binding Plugin feature is GA and enabled by default. | |
| > No feature gate activation is required. | |
| As of v1.5.0, the Network Binding Plugin feature enabled by default and has no feature gate. | |
| The passt plugin similarly has no feature gate of its own, but the plugin needs to be made available in the cluster by [registering it](./#passt-registration). |
Comment on lines
146
to
147
| > **Note**: As of v1.5.0, the Network Binding Plugin feature is GA and enabled by default. | ||
| > No feature gate activation is required. |
There was a problem hiding this comment.
As of v1.5.0, the Network Binding Plugin feature enabled by default and has no feature gate.
The macvtap plugin similarly has no feature gate of its own, but the plugin needs to be made available in the cluster by registering it.
Comment on lines
149
to
150
| > **Note**: The specific macvtap plugin has no feature gate of its own. It is up to the cluster | ||
| > admin to decide if the plugin is to be available in the cluster by registering it. |
There was a problem hiding this comment.
If the above suggestion looks good, remove this note.
Comment on lines
+124
to
+126
|
|
||
| > **Important**: The core macvtap binding was discontinued and removed in v1.3.0 (deprecated in v1.2.0). | ||
| > This documentation covers the **network binding plugin** implementation of macvtap. |
There was a problem hiding this comment.
Suggested change
| > **Important**: The core macvtap binding was discontinued and removed in v1.3.0 (deprecated in v1.2.0). | |
| > This documentation covers the **network binding plugin** implementation of macvtap. | |
| The experimental core macvtap binding was discontinued and removed in v1.3.0 (deprecated in v1.2.0). | |
| This documentation covers the **network binding plugin** implementation of macvtap. |
Comment on lines
128
to
129
| The binding plugin replaces the experimental core macvtap binding implementation | ||
| (including its API). |
There was a problem hiding this comment.
We can now remove this as it's covered in more specific detail in the previous line
Comment on lines
131
to
132
| > **Note**: The network binding plugin infrastructure is GA as of v1.5.0. | ||
| > The macvtap plugin is stable for production use. |
- Update network binding plugins feature status from Beta to GA (v1.5.0) - Remove version-specific tags from plugin listings and main page - Update passt, slirp, and macvtap plugin documentation: - Remove Alpha/Beta status warnings and redundant production notes - Update feature gate requirements (now GA by default) - Clarify core binding vs plugin distinctions for slirp and macvtap - Add important notes about removed core bindings - Standardize messaging and improve text consistency across all files - Remove redundant phrasing and unnecessary sections Fixes: kubevirt#918 Co-Authored-By: Claude <[email protected]> Signed-off-by: Andrew Burden <[email protected]>
aburdenthehand
force-pushed
the
feature-lifecycle-updates-network
branch
from
4da45da to
1dde4f5
Compare
8 tasks
kubevirt-bot
added
the
needs-rebase
|
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #918
Additional context:
Release note: