community
community copied to clipboard
tektoncd
TEP-0085: Per-Namespace Controller Configuration [Proposal]
In TEP-0085 we proposed the support for overriding tekton-pipelines-controller's configuration on a per-namespace basis.
In this pull request, we include the proposal to configure the feature-flags configuration per namespace which is implemented in Tekton Pipelines Pull Request #4499
In summary, we propose enabling the controller's feature flags configuration per namespace via a new feature-flags ConfigMap in each of the candidate namespaces to override the properties defined in the feature-flags ConfigMap in the default system namespace, and the candidate namespaces are included in a new environment variable in the tekton-pipelines-controller.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign khrm
You can assign the PR to them by writing /assign @khrm in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
thank you @leiyanggz 😸
/assign
cc @sbwsg @vdemeester @pritidesai @dibyom (from the problem statement - https://github.com/tektoncd/community/pull/506)
Please add yourself as author and set the status to implementable:
status: implementable
title: Per-Namespace Controller Configuration
creation-date: '2021-08-25'
last-updated: '2022-01-24'
authors:
- '@sbwsg'
- '@jerop'
- '@leiyanggz'
@leiyanggz - please join us in one of the API WG on Mondays 12pm ET to discuss the review comments in this TEP and move it forward, happy to schedule an ad-hoc meeting if the time doesn't work for you, please let us know :)
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopenwith a justification. Mark the issue as fresh with/remove-lifecycle rottenwith a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozenwith a justification./close
Send feedback to tektoncd/plumbing.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.