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

DO280-4.12 Feedback: In Step 9.5 of the Cluster Self-Service Setup lab, it mentions using this label/value: "network.open...

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • 10
    • en-US (English)
    • DO280 Sprint 1, DO280 Sprint 2

      Please fill in the following information:


      URL: https://rol.redhat.com/rol/app/courses/do280-4.12/pages/ch10s02
      Reporter RHNID: shasingh01
      Section title:

      Lab: Cluster Self-service Setup

      Language:                                                                        

      Issue description

      Description:  In Step 9.5 of the Cluster Self-Service Setup lab, it mentions using this label/value: "network.openshift.io/policy-group: ingress" I am practicing looking things up in the documentation (there's still way too much rote memorisation for me to deal with this successfully). And I happened to notice I was having a tough time searching for "network.openshift.io/policy-group" but I eventually figured out how to find it and apparently this is now a legacy label and "policy-group.network.openshift.io/ingress has become the preferred namespace selector label for OpenShift SDN[1]. What I'm wondering is: Are both of these acceptable for grading? Would the new label, if I happened upon it and used it instead, still work in an exam environment? https://docs.openshift.com/container-platform/4.12/networking/network_policy/multitenant-network-policy.html 

      Steps to reproduce:

      policy-group.network.openshift.io/ingress: "" is the preferred namespace selector label for OpenShift SDN

      network.openshift.io/policy-group: ingress namespace selector label, but this is a legacy label.

      Workaround:

       

      Expected result:

            althomas@redhat.com Allen Thomas
            shasingh01 Shashi Singh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: