Story (Required)

Similar to Chains, PAC, Triggers, results should be installed by default.

Background (Required)

Out of scope

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)

• Upgrade from TektonResult to autogenerated by TektonConfig should be enabled.
• Automation of installation process. TLS secret creation. DB Secrets.{}
• Results should be installed by default unless enabled is set to false.
• Statefulset of DB should be deleted on change.
• Recreate API server if config map changes.
• e2e tests to cover the above.

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