Skip to content

SR-IOV Network Operator configuration #16679

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.

Sign up for GitHub

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

Merged
jboxman merged 1 commit into from
Nov 8, 2019
Merged

SR-IOV Network Operator configuration #16679

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
314 changes: 0 additions & 314 deletions modules/nw-multinetwork-sriov.adoc
View file
Open in desktop

This file was deleted.

20 changes: 19 additions & 1 deletion modules/nw-multus-add-pod.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,31 @@
//
// * networking/multiple-networks/attaching-pod.adoc

ifeval::["{context}" == "configuring-sr-iov"]
:sriov:
endif::[]

[id="nw-multus-add-pod_{context}"]
= Adding a Pod to an additional network

You can add a Pod to an additional network. The Pod continues to send normal
cluster related network traffic over the default network.

ifdef::sriov[]
[NOTE]
=====
The Network Resources Injector will inject the `resource` parameter into the Pod CR automatically if a NetworkAttachmentDefinition CR associated with the SR-IOV CNI plug-in is specified.
=====
endif::sriov[]

.Prerequisites

* The Pod must be in the same namespace as the additional network.
* Install the OpenShift Command-line Interface (CLI), commonly known as `oc`.
* You must log in to the cluster.
ifdef::sriov[]
* You must have the SR-IOV Operator installed and a SriovNetwork CR defined.
endif::sriov[]

.Procedure

Expand Down Expand Up @@ -63,7 +77,7 @@ spec:
following command. Replace `<name>` with the name of the Pod.
+
----
$ oc describe pod <name>
$ oc get pod <name> -o yaml
----
+
In the following example, the `example-pod` Pod is attached to the `net1`
Expand Down Expand Up @@ -104,3 +118,7 @@ status:
<1> The `k8s.v1.cni.cncf.io/networks-status` parameter is a JSON array of
objects. Each object describes the status of an additional network attached
to the Pod. The annotation value is stored as a plain text value.

ifeval::["{context}" == "configuring-sr-iov"]
:!sriov:
endif::[]
Loading