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

use of deprecated cluster task in pipeline example.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • DO288 - RHOCP4.18-en-2-20250829
    • DO288
    • False
    • Hide

      None

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

      Please fill in the following information:


      URL:  
      Reporter RHNID: bucknd
      Section Title:                   defining pipelines                                                     

      Issue description

      1.  In this section it states "the following example pipeline uses the provided git-clone cluster task to retrieve a repository"

      As it appears there are no cluster tasks installed and the graphic reference 3 states "References the git-clone task from the openshift-pipelines namespace" I am guessing that this should not be using a cluster task as the tasks in that project are not cluster tasks and cluster tasks are deprecated in any case -the jargon should be adjusted so as not to confuse cluster tasks with tasks accessed using cluster resolver

       

      2.  An additional problem in this area is the example used of

      tkn -n openshift-pipelines t describe buildah

      as it fails if you run it as developer but works as admin whereas 

      tkn -n openshift-pipelines t list

      does work for developer. Why can a developer not query this resource with tkn? is a problem with permissions in the classroom or is there an operator installation bug causing this ?

       

      3.  in the task and pipeline runs section it states

      "Creating a task run from the following example task run manifest starts a task called git-clone that fetches an application"

      The relevant part of the yaml that shows the name of the task being called has been omitted. It should be shown in the yaml

       

      4.  in the section accessing secure image registry with openshift pipelines students are told to create a secret manually from a piece of yaml which is legitimate given the specific attributes that need to be set on it. However it then advocates creating yaml to create a new service account and also to associate the service account with the pipelinerun and taskrun when the oc set serviceaccount and oc secret link commands were taught to them in chapter 5 so why make things more difficult now, especially as the exercise uses this method anyway. it makes learning unnecessarily complicated

       

      5.  tkn bash completion is not configured. Make the system as simple as possible to use for the new learner

      Steps to reproduce:

       

      Workaround:

       

      Expected result:

              rht-eramirez Eduardo Ramirez
              bucknd David Bucknell
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: