passt: Fix docs

Update docs about cni daemonSet.
Update outdated parts.

Signed-off-by: Or Shoval <[email protected]>

Author: oshoval

docs/network/net_binding_plugins/passt.md

@@ -74,22 +74,80 @@ the passt plugin needs to:
 And in detail:
 
 ### Passt CNI deployment on nodes
-The CNI plugin binary can be retrieved directly from the kubevirt release
-assets (on GitHub) or to be built from its
+
+#### prior to v1.6.0
+The CNI binary can be retrieved directly from the kubevirt release assets (on GitHub) or to be built from its
 [sources](https://github.com/kubevirt/kubevirt/tree/release-1.1/cmd/cniplugins/passt-binding).
 
 > **Note**: The kubevirt project uses Bazel to build the binaries and container images.
 > For more information in how to build the whole project, visit the developer
 > [getting started guide](https://github.com/kubevirt/kubevirt/blob/release-1.1/docs/getting-started.md).
 
-Once the binary is ready, you may rename it to a meaningful name
-(e.g. `kubevirt-passt-binding`).
+Once the binary is ready, you may rename it to a meaningful name (e.g. `kubevirt-passt-binding`).
 This name is used in the NetworkAttachmentDefinition configuration.
 
 Copy the binary to each node in your cluster.
 The location of the CNI plugins may vary between platforms and versions.
 One common path is `/opt/cni/bin/`.
 
+#### starting with v1.6.0
+Kubevirt releases a container image `quay.io/kubevirt/network-passt-binding-cni:v1.6.0`,
+which can be used via daemonSet to copy the CNI binary to the nodes.
+
+Create the following DaemonSet:
+
+```yaml
+apiVersion: apps/v1
+kind: DaemonSet
+metadata:
+  name: passt-binding-cni
+  namespace: kubevirt
+  labels:
+    tier: node
+    app: passt-binding-cni
+spec:
+  selector:
+    matchLabels:
+      name: passt-binding-cni
+  updateStrategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxUnavailable: 10%
+  template:
+    metadata:
+      labels:
+        name: passt-binding-cni
+        tier: node
+        app: passt-binding-cni
+      annotations:
+        description: passt-binding-cni installs 'passt binding' CNI on cluster nodes
+    spec:
+      priorityClassName: system-cluster-critical
+      containers:
+      - name: installer
+        image: quay.io/kubevirt/network-passt-binding-cni:v1.6.0
+        command: [ "/bin/sh", "-ce" ]
+        args:
+        - |
+          ls -la "/cni/kubevirt-passt-binding"
+          cp -f "/cni/kubevirt-passt-binding" "/opt/cni/bin"
+          echo "passt binding CNI plugin installation complete..sleep infinity"
+          sleep 2147483647
+        resources:
+          requests:
+            cpu: "10m"
+            memory: "15Mi"
+        securityContext:
+          privileged: true
+        volumeMounts:
+        - name: cnibin
+          mountPath: /opt/cni/bin
+      volumes:
+      - name: cnibin
+        hostPath:
+          path: /opt/cni/bin
+```
+
 ### Passt NetworkAttachmentDefinition
 The configuration needed for passt is minimalistic:
 
@@ -123,16 +181,20 @@ The sidecar sources can be found
 The relevant sidecar image needs to be accessible by the cluster and
 specified in the Kubevirt CR when registering the network binding plugin.
 
-### Feature Gate
-If not already set, add the `NetworkBindingPlugins` FG.
+### Feature Gate - for KubeVirt versions prior to v1.5
+If not already set, add the `NetworkBindingPlugins` Feature Gate.
 ```
-kubectl patch kubevirts -n kubevirt kubevirt --type=json -p='[{"op": "add", "path": "/spec/configuration/developerConfiguration/featureGates/-",   "value": "NetworkBindingPlugins"}]'
+kubectl patch kubevirt -n kubevirt kubevirt --type=merge -p='{"spec":{"configuration":{"developerConfiguration":{"featureGates":["NetworkBindingPlugins"]}}}}'
 ```
 
 > **Note**: The specific passt plugin has no FG by its own. It is up to the cluster
 > admin to decide if the plugin is to be available in the cluster.
 > The passt binding is still in evaluation, use it with care.
 
+**Note**: 
+> It is up to the cluster admin to decide if the plugin is to be available in the cluster.
+> The passt binding is still in evaluation, use it with care.
+
 ### Passt Registration
 As described in the [registration section](../../network/network_binding_plugins.md#register), passt binding plugin
 configuration needs to be added to the kubevirt CR.
@@ -143,11 +205,11 @@ kubectl patch kubevirts -n kubevirt kubevirt --type=json -p='[{"op": "add", "pat
             "binding": {
                 "passt": {
                     "networkAttachmentDefinition": "default/netbindingpasst",
-                    "sidecarImage": "quay.io/kubevirt/network-passt-binding:20231205_29a16d5c9",
+                    "sidecarImage": "quay.io/kubevirt/network-passt-binding:v1.6.0",
                     "migration": {},
                     "computeResourceOverhead": {
                       "requests": {
-                        "memory": "500Mi",
+                        "memory": "250Mi",
                       }
                     }
                 }
@@ -159,7 +221,7 @@ The NetworkAttachmentDefinition and sidecarImage values should correspond with t
 names used in the previous sections, [here](#passt-networkattachmentdefinition)
 and [here](#passt-sidecar-image).
 
-When using the plugin, additional memory overhead of `500Mi` will be requested for the compute container in the virt-launcher pod.
+When using the plugin, additional memory overhead of `250Mi` will be requested for the compute container in the virt-launcher pod.
 
 When the VM boots for the first time, Passt's internal DHCP server assigns an IP address to the guest with an "infinite" lease duration.
 
@@ -222,7 +284,7 @@ spec:
       terminationGracePeriodSeconds: 0
       volumes:
       - containerDisk:
-          image: quay.io/kubevirt/fedora-with-test-tooling-container-disk:v1.1.0
+          image: quay.io/kubevirt/fedora-with-test-tooling-container-disk:v1.6.0
         name: containerdisk
       - cloudInitNoCloud:
           networkData: |