Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-8503

Upstream release notes for results

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • Pipelines 1.20.0
    • Pipelines 1.20.0
    • Tekton Results
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Features:
      Add anti-affinity rules to results's replicas: This ensure that if multiple replicas of watcher are deployed as HA, they don't end up in same node.

      With this release, you can use a flag to Disable Live Collection of Runs in tektonconfig's result field:
      results:
        options:
          deployments:
            tekton-results-watcher:
              spec:
                template:
                  spec:
                    containers:
                    - name: watcher
                      args:
                      - "--disable_storing_incomplete_runs=true"
      If set to true, Runs will not be stored until they are complete. If false, Runs will be initially stored upon creation and continuously upserted until after they're deleted. Latter is the default behaviour, but we recommend moving to former as it's more performant. We will move away to former behaviour as default soon.

      All the results' container have readOnlyRootFilesystem set.

      Deprecation:
      In retention agent, we have deprecated `maxRetention` parameter in favour of `defaultRetention`.
      Show
      Features: Add anti-affinity rules to results's replicas: This ensure that if multiple replicas of watcher are deployed as HA, they don't end up in same node. With this release, you can use a flag to Disable Live Collection of Runs in tektonconfig's result field: results:   options:     deployments:       tekton-results-watcher:         spec:           template:             spec:               containers:               - name: watcher                 args:                 - "--disable_storing_incomplete_runs=true" If set to true, Runs will not be stored until they are complete. If false, Runs will be initially stored upon creation and continuously upserted until after they're deleted. Latter is the default behaviour, but we recommend moving to former as it's more performant. We will move away to former behaviour as default soon. All the results' container have readOnlyRootFilesystem set. Deprecation: In retention agent, we have deprecated `maxRetention` parameter in favour of `defaultRetention`.
    • Unspecified Release Note Type - Unknown
    • Done
    • Pipelines Sprint Crookshank 37

      Story (Required)

      Any relevant RN from upstream needs to be added to the release notes section in a consolidated manner and docs team will be referring to this instead of google docs moving forward.

      Background (Required)

      <Describes the context or background related to this story>

      Out of scope

      • Drafting the release notes text.
      • Review and approval of release notes.
      • Publication of the release notes.

      Approach (Required)

      • Fetch the list of PRs/issues merged upstream for v1.20 from GitHub (tektoncd/results {}repo).
      • Identify PRs relevant to OpenShift Pipelines (skip upstream-only changes not consumed downstream, if applicable).
      • Organize contributions into categories (features, enhancements, bug fixes).

      Dependencies

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

      Acceptance Criteria (Mandatory)

      RN section is added with a consolidated list of revelant upstream release notes.

      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

              rh-ee-kbaig Khurram Baig
              rh-ee-pbheeman Pavan Mandayam Bheeman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: