-
Story
-
Resolution: Done
-
Critical
-
None
-
3
-
False
-
None
-
False
-
-
-
3
-
Pipelines Sprint 231, Pipelines Sprint 232, Pipelines Sprint 234, Pipelines Sprint 236, Pipelines Sprint 237
Story (Required)
As a cluster-admin trying to change some performance related flags on the tektoncd-pipeline controller I want to be able to do this through the operator configuration (TektonConfig)
The idea is to allow cluster-admins to configure their pipeline controller instance "with ease" so that their instance can handle more objects.
This is the design phase
Background (Required)
Link to support case (https://access.redhat.com/support/cases/#/case/03386276) and workaround issue .
Out of scope
- Possibly other controller's option
Approach (Required)
2 ways:
- Expose some "controller extra flags" field for the pipeline part of TektonConfig
- Expose some "generic extra flags" or "mutation expression" on the main TektonConfig (that could target any payload managed by the controller)
Acceptance Criteria (Mandatory)
I can set performance flags (QPS, …) from the operator without having to patch the TektonInstallerSet
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
- relates to
-
SRVKP-3224 Allow additional fields in the operator
- Closed