-
Epic
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
Per-namespace configuration
-
False
-
None
-
False
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
-
Epic Goal
This Epic proposes support for overriding Tekton Pipelines' configuration on a per-namespace basis.
See https://github.com/tektoncd/community/blob/main/teps/0085-per-namespace-controller-configuration.md
Why is this important?
- improve flexibility for organizations gradually migrating their teams during Tekton's infrequent (but potentially disruptive) behavioural changes
- allow platforms and organizations to apply finer-grained configurations, such as individualized RBAC on a per-tenant basis
- improve a key portion of our own open source testing strategy by allowing configuration changes to be exercised in isolated namespaces rather than entirely separate clusters
Scenarios
- ...
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
- duplicates
-
-
- To Do
-
