Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-6099

DOC: [TEP-0094] Promote taskrun.spec's stepSpecs and sidecarSpecs to beta

XMLWordPrintable

    • 3
    • Documentation (Ref Guide, User Guide, etc.), User Experience
    • Hide
      You can now set stepSpecs and sidecarSpecs for taskrun.
      e.g.: apiVersion: tekton.dev/v1
      kind: Task
      metadata:
        name: side-step
      spec:
        steps:
          - name: test
            image: docker.io//alpine:latest
        sidecars:
          - name: side
            image: docker.io/linuxcontainers/alpine:latest
      ---
      apiVersion: tekton.dev/v1
      kind: TaskRun
      metadata:
        name: test-sidestep
      spec:
        taskRef:
          name: side-step
        stepSpecs:
          - name: test
            computeResources:
              requests:
                memory: 1Gi
        sidecarSpecs:
          - name: side
            computeResources:
              requests:
                cpu: 100m
              limits:
                cpu: 500m
      Show
      You can now set stepSpecs and sidecarSpecs for taskrun. e.g.: apiVersion: tekton.dev/v1 kind: Task metadata:   name: side-step spec:   steps:     - name: test       image: docker.io//alpine:latest   sidecars:     - name: side       image: docker.io/linuxcontainers/alpine:latest --- apiVersion: tekton.dev/v1 kind: TaskRun metadata:   name: test-sidestep spec:   taskRef:     name: side-step   stepSpecs:     - name: test       computeResources:         requests:           memory: 1Gi   sidecarSpecs:     - name: side       computeResources:         requests:           cpu: 100m         limits:           cpu: 500m
    • ---
    • ---

      Story (Required)

      We need to promote taskrun.spec's stepSpecs and sidecarSpecs to beta. It was introduced in v0.34.0 of Tekton Pipelines.

      Background (Required)

      Customers are requesting to set taskrun.spec's stepSpecs and sidecarSpecs .  This can't be done without setting API to alpha which isn't supported. We need to promote to beta.

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              mramendi Mikhail Ramendik
              mramendi Mikhail Ramendik
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: