SDN-1334: Pod to svc connectivity check in OVN

[tssurya]

What is the aim of the script?

Test connectivity between pod and svc in OVN. It runs ovnkube-trace between the pod and svc in case of connectivity failure to check what went wrong.

How to test the script?

The script assumes that $KUBECONFIG file is loaded/mounted at /tmp/kubeconfig inside the pod. This is just temporary and will go away once we add a serviceaccount for the debug-namespace.

Method 1: Launch a debug pod on an OCP OVN cluster:

Sample yaml:

---
apiVersion: v1
kind: Pod
metadata:
  name: pod1
  labels:
    app: MyApp
spec:
  containers:
  - name: pod1
    image: quay.io/itssurya/dev-images:15084af4-4491-44a2-94bf-c62bfdeb7131
    command:
      - /sbin/init

Replace the image with registry.svc.ci.openshift.org/ocp/4.7:ocp-debug-network once the image lands in the registry.

oc rsh -n <DEBUG-NETWORK-NAMESPACE> <debug-network-podname> ./usr/bin/debug-network-scripts/ovn/pod_to_svc.sh <src-node-name> <dst-node-name>

Method 2: Launch it via podman or docker:

podman run -v /tmp/kubeconfig:/tmp/kubeconfig <IMAGE_ID> ./usr/bin/debug-network-scripts/ovn/pod_to_svc.sh

[tssurya]

/hold

[tssurya]

/hold cancel.

This is good to go.

[tssurya]

/hold cancel

[juanluisvaladas]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: juanluisvaladas, tssurya

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [juanluisvaladas]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tssurya]

This is done to keep the directory structure and avoid overwriting sdn and ovn files with the same name. We can clean it up in the future for when we integrate with oc adm and invoke the scripts.

[juanluisvaladas]

Good enough, this will be reworked next week anyway