Configuring Multihomed Nodes and Virtual Machines

[Ravi_Shanker]

https://rol.redhat.com/rol/app/courses/do316-4.16/pages/ch04s03

In this chapter slide there are two images explained one is for 

Kubernetes NMState with Multus in OpenShift Virtualization

and second one is for 

OVS Bridge Overview

However 2nd image is just a copy of first image and is not explaining the concept of OVS Bridge in VM network communication to other networks.

Need clarification if my understanding from the image is wrong or the image is indeed incorrect.

Thanks in Advance

Ravi Shanker

[Chetan_Tiwary_]

@Ravi_Shanker Let me check this one for you.

[Chetan_Tiwary_ · Accepted solution]

Hey @Ravi_Shanker you are right and it seems a typo/misprint. I have alerted the devs for the same and they have replied that either they will remove it or replace with a suitable graphics.

Thank you for reporting this to us! Your feedback help us make our courses better!

[Ravi_Shanker]

There is one more error in https://rol.redhat.com/rol/app/courses/do316-4.16/pages/ch03s06 exercise solution.

Guided Exercise: Configure External Access to a Virtual Machine:

Point 7 , 7.1.

The solution mentions exit code 28 which is wrong. The video solution shows the correct solution which is success for welcome page as the URL access is happening from router pod and router pod is allowed access as per network policy.

[student@workstation ~]$ oc rsh $PODNAME curl --max-time 5 \
  hello-web-web-servers.apps.ocp4.example.com | grep Welcome command terminated with exit code 28

[Chetan_Tiwary_]

@Ravi_Shanker Regret the incovenience caused! I think the course step 7 seems right because it should fail as the test-project namespace does not have access, because network policy requires access via the pods in the ingress controller namespace.

There was an udate to the network policy which has messed up - let me alert the devs regarding this.

Again thank you for pointing it out!

[Ravi_Shanker]

@Chetan_Tiwary_  when a route URL is being accessed is it not coming from the router pod in openshift-ingress namespace ? If the route URL is allowed by including the label on openshift-ingress project in the network policy then the applied network policy does not block access for route url. 

The outcomes of the lab mentions:

• Update the network policy to allow traffic from the route.

• Solution is not representing the desired outcome:

• [student@workstation ~]$ oc rsh $PODNAME curl --max-time 5 \
    hello-web-web-servers.apps.ocp4.example.com | grep Welcome   command terminated with exit code 28

[Chetan_Tiwary_]

@Ravi_Shanker I have escalated this to the devs for more information on the same. Let me get back to you with more details.