oshoval

1. Make sure you are use sslip, and have a valid pull secret.
2. Copy the kubeconfig from your remote machine to your local, export KUBECONFIG pointing to it.
3. Change kubeconfig `server` line to match your remote machine ip i.e `server: 10.1.2.3:6443` (keep original port).
4. On your local machine run the following command in the background `sshuttle -r root@your_hypervisor 192.168.122.0/24`
5. Open the console URL, i.e `console-openshift-console.apps.multi-homing.192-168-122-253.sslip.io` on your local chrome (get it via oc get routes -A).

oshoval

#!/bin/bash -ex

# Enabling OpenShift FeatureSet on KCLI makes the cluster unstable, hence lets enable specifically just what needed.

# Make sure you have the desired KCLI / HCO nighly deployed (this doc doesnt cover it).
# See https://access.redhat.com/articles/6070641

# This script enables only OCP features, not HCO ones.

oc patch network.operator.openshift.io cluster --type='merge' -p='{"spec":{"managementState":"Unmanaged"}}'

RamLavi

# Overview
The following depict example manifests of two scenarios of communication between VMs connected via primay-UDN:
1. VMs under the same namespace
2. VMs under different namespaces

## Prerequisits
- CNV 4.17 cluster.
- oc tool

# Configuring priamry-UDN on a CNV cluster

qinqon

This is the nad + vmi

---
apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
  name: l2-network
spec:
  config: |2
    {

lmilleri

vDPA on ovn-k secondary network

Getting Started

These instructions will let you to create pods consuming accelerated vDPA interfaces on ovn-k secondary network

Prerequisites

• OCP cluster running (latest 4.14)
• SRIOV network operator is installed (latest upstream)
• kubernetes-nmstate operator is installed (latest downstream)
• ovn-kubernetes running image is quay.io/rh_ee_lmilleri/ovn-daemonset-f:vhost-vdpa-0906-3

oshoval

1. Install kcli
   https://kcli.readthedocs.io/en/latest/index.html#deploying-kubernetes-openshift-clusters-and-applications-on-top

2. Get a pull secret, save as openshift-pull-secret.json
   https://console.redhat.com/openshift/create/local

3. Create a secondary network
   kcli create network -c 192.168.20.0/24 secondary

4. Create this yaml, save as parameters.yml

ormergi

# This script enable faster development iterations in Kubevirt
# when working on a change that might affect backward compatibility,
# upgrades or legacy VMs (a VM that existed before an upgrade) disruption.
#
# Use case:
# 1. Changing virt-launcher pods secondary networks interfaces name scheme.
#    Different network interfaces name-schemes breaks migration for legacy VMs
#    when Kubevirt is updated.
#
#    In order to test this, its necessary to have both versions images,