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

Upstream release notes for Operator

XMLWordPrintable

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

      None

      Show
      None
    • False
    • Hide
       1) Add init container support to tekton-operator deployment (#2809):
            Allow configuring init containers in the Helm chart deployment template when operator.initContainers.enabled is set to true.
            Usage example: We use this to inject a initContainer before Tekton Operator bootup

      2) Add service monitoring for pruner (#2844)
          A new ServiceMonitor resource has been introduced to enable monitoring of the Tekton Pruner controller.

      3) update s2i image (#2837)
          Updated S2I image to FIPS-compliant version

      4) Update OPC task image reference in OpenShift config (#2825)

      5) Add buildah-ns task as a part of openshift-pipelines namespace (#2824)

      6)fix(openshift git resolver): mount the trusted-ca-configmap into component's system ca store in Openshift (#2814)
        
      7) fix: prevent panic when pruner field is nil during upgrade (#2810)
      Show
       1) Add init container support to tekton-operator deployment (#2809):       Allow configuring init containers in the Helm chart deployment template when operator.initContainers.enabled is set to true.       Usage example: We use this to inject a initContainer before Tekton Operator bootup 2) Add service monitoring for pruner (#2844)     A new ServiceMonitor resource has been introduced to enable monitoring of the Tekton Pruner controller. 3) update s2i image (#2837)     Updated S2I image to FIPS-compliant version 4) Update OPC task image reference in OpenShift config (#2825) 5) Add buildah-ns task as a part of openshift-pipelines namespace (#2824) 6)fix(openshift git resolver): mount the trusted-ca-configmap into component's system ca store in Openshift (#2814)    7) fix: prevent panic when pruner field is nil during upgrade (#2810)
    • Unspecified Release Note Type - Unknown
    • Done
    • Pipelines Sprint Pioneers 36, Pipelines Sprint Pioneers 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/operator 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

              jkhelil abdeljawed khelil
              rh-ee-pbheeman Pavan Mandayam Bheeman
              Pavan Mandayam Bheeman Pavan Mandayam Bheeman
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: