-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
False
-
None
-
False
-
-
Story (Required)
Users should be able to add init, side or other containers in the deployment using options field.
Background (Required)
This can be required in case if some mesh service container is needed or some auth containers like kube rbac proxy is needed for metrics.
Results in Konflux uses kube rbac proxy to manage access to metrics endpoints. Shifting to operator install forces us to downgrade from this practice.
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
Acceptance Criteria (Mandatory)
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