• Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • 5
    • True
    • Hide

      Requires completion of https://issues.redhat.com/browse/DEVAI-31 to test the new pipeline definitions against the new config setup for tekton. Currently can be tested against RHTAP with TAS/TPA/ACS disabled however I can't guarantee they will be the same setup. With that being said I need to test against the new tekton config before this issue can be closed

      Show
      Requires completion of https://issues.redhat.com/browse/DEVAI-31 to test the new pipeline definitions against the new config setup for tekton. Currently can be tested against RHTAP with TAS/TPA/ACS disabled however I can't guarantee they will be the same setup. With that being said I need to test against the new tekton config before this issue can be closed
    • False
    • DEVAI Sprint 3262, DEVAI Sprint 3263

      Task Description (Required)

      As part of the overall setup for pipelines and tekton along with the service configuration (DEVHAS-765), we need a modified pipeline definition for AI Software Templates to remove dependencies of unused services from RHTAP: ACS, TAS, and TPA.

      We'll need to create fork of https://github.com/redhat-appstudio/tssc-sample-pipelines to store a modified pipeline definition without the mentioned unused services. After creating the pipeline defintion we'll need to change our current references to use ours instead of the one for RHTAP: https://github.com/redhat-ai-dev/ai-lab-template/blob/8b8db05b3e53c0333fca64f0c04d1e451b333f06/scripts/update-tekton-definition#L6
       

      If this requires Change Management, complete sections below: 

      Change Request 

       

      <Select which item is being changed>

       

      [ ]  Add New Tokens

      [ ]  Rotate Tokens

      [ ]  Remove Tokens

      [ ] Others: (specify)

       

        Environment

      <Select which environment the change is being made on.  If both, open a separate issue so changes are tracked in each environment>

       

      [ ]  Stage OR

      [ ]  Prod

       

        Backout Plan

      <State what steps are needed to roll back in case something goes wrong>

       

        Downtime

      <Is there any downtime for these changes?  If so, for how long>

       

        Risk Level

      <How risky is this change?>

       

        Testing

      <How are changes verified?>

       

        Communication

      <How are service owners or consumers notified of these changes?>

              rh-ee-jdubrick Jordan Dubrick
              mvaldron Michael Valdron
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: