feat(tekton): reconcile url-shortener CI with scoped RBAC
This commit is contained in:
1 parent
6df004a1da
commit
1e20c435cd
3 files changed
+71
No files matched your search
@@ -87,6 +87,27 @@ service-state/
|
||||
Tekton controllers stay in `tekton-pipelines`. Application PipelineRuns and
|
||||
their credentials run in the isolated `tekton-ci` namespace.
|
||||
|
||||
## Registering Additional Service CI
|
||||
|
||||
CI directories in `service-state` are registered explicitly; the service
|
||||
ApplicationSets discover only `apps/*/overlays/*`.
|
||||
|
||||
For URL shortener, `argocd/applications/url-shortener-ci.yaml` reconciles
|
||||
`service-state/ci/url-shortener` into `tekton-ci` using the `ci` project.
|
||||
The platform root Application discovers this registration recursively.
|
||||
|
||||
Cluster-scoped EventListener RBAC belongs in
|
||||
`platform/tekton/config/eventlistener-rbac.yaml`. Each listener receives a
|
||||
dedicated ClusterRole and ClusterRoleBinding allowing only `get`, `list`, and
|
||||
`watch` on `clusterinterceptors` and `clustertriggerbindings`.
|
||||
Keep ServiceAccounts, Roles, and RoleBindings in `service-state`; remove the
|
||||
URL shortener ClusterRoleBinding from its `foundation.yaml` when adopting this
|
||||
registration. The `ci` project intentionally does not allow cluster resources.
|
||||
|
||||
Before the first URL shortener run, configure its Infisical secrets and Gitea
|
||||
push webhook at `https://tekton-hook.dahyeon.us/url-shortener` as defined in
|
||||
`service-state/ci/url-shortener`.
|
||||
|
||||
## Code Style
|
||||
|
||||
Use stable Tekton APIs, explicit names, immutable image references, bounded
|
||||
|
||||
Reference in new issue
Block a user