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

DO380-205, Ch02s02: querying the OSP webconsole can be easier

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Minor Minor
    • DO380 - OCP4.10-en-3-20221129
    • DO380
    • None
    • 2
    • ROLE
    • en-US (English)

      URL: https://role.rhu.redhat.com/rol-rhu/app/courses/do380-4.10/pages/ch02s02
      Reporter RHNID: ctiwary@redhat.com
      Section: 2 - Guided Exercise: Querying OpenShift Resources
      Language: en-US (English)
      Workaround:

      Description: RHT2015416 : Section 2.2, Step 1.2 of the Querying OpenShift guided exercise has a convoluted process to get and query the web console when it could just be this: ``` $ console=$(oc whoami --show-console) $ curl -I $console ``` I can appreciate the possibility it is showing jsonpath and I appreciate the argument that someone should be able to work with that in "such an advanced course" but there are better opportunities to teach jsonpath when we would like administrators to know the flags to `oc whoami` that show server, console, token, and other information or more of a dive into the openshift console project, operator, routes, etc.

              rht-bgargallo Bernardo Andres Gargallo Jaquotot
              chetan-rhls Chetan Tiwary
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: