-
Story
-
Resolution: Unresolved
-
Blocker
-
None
-
8
-
Documentation (Ref Guide, User Guide, etc.), User Experience
-
---
-
---
Epic Goal
- This covers the issues which can be features or bugs that we need to GA the results.
Why is this important?
Scenarios
- The end user should be able to install Results using Tekton Config
- Rest APIs shouldn't do translation to GRPC.
- Add Index for performance.
- Automation of installation process. TLS secret creation. DB Secrets.
- Results API Config should change from env to yaml format like other components. It's easier to use in options.
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment
- clones
-
SRVKP-6185 Tekton Results GA
- In Progress
- documents
-
SRVKP-6185 Tekton Results GA
- In Progress
- links to