Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-15997

UDN graphic figure 14 is confusing

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • DO280 - RHOCP4.18-en-1-20251205
    • DO280
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 5
    • en-US (English)

      Please fill in the following information:


      URL: https://rol.redhat.com/rol/app/courses/do280-4.18/pages/ch05s03
      Reporter RHNID: bucknd
      Section Title:                  user defined networks                                                      

      Issue description

      I find figure 14 confusing as it implicitly includes features that are not relevant to the usage of the UDN. A simpler graphic might be better to focus the student’s mind on the actual learning point. If my interpretation of the graphic is missing detail that I have overlooked it is important therefore that this additional information be added into the student guide so the student has a complete understanding of what is being presented by the graphic. My interpretation of the learning point is simply to show one network for each namespace. The issues with the current graphic are:

      • the graphic is showing two replicas for each pod. Why would pod1 and pod2 replicas both be scheduled on the same node – the scheduler would more likely run the replicas on different nodes. This might cause unnecessary confusion and questions
      • the two replicas for pod3 are in two different namespaces. If the two pod3 pods are indeed replicas they would not be in different namespaces
      • why not keep the graphic simple so as not to hide the important learning point, i.e. only have one pod on each node only with 3 different pods in each namespace – just using one or two nodes would work equally well and be clearer as the main teaching point seems to be the fact that all the pods in the namespace can talk to each other but not the pods in the other namespace, with the node being ‘irrelevent’

      Steps to reproduce:

       

      Workaround:

       

      Expected result:

              gls-curriculum-ocp-core@redhat.com PTL - OCP Platform Team
              bucknd David Bucknell
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: