docs: add Tekton external setup steps

This commit is contained in:
dahyeon committed 2026-07-18 08:26:11 +00:00
1 parent b14c8e5b43
commit 2d0df191dc
1 file changed
+16 -1
+16 -1
View File
@@ -107,12 +107,15 @@ spec:
script: | script: |
#!/bin/sh #!/bin/sh
set -eu set -eu
corepack pnpm --filter api test -- --runInBand pnpm --filter api test --runInBand
``` ```
Do not use mutable image tags such as `latest`, inline credentials, or direct Do not use mutable image tags such as `latest`, inline credentials, or direct
`kubectl set image` deployment mutations. `kubectl set image` deployment mutations.
The pinned Node 26 image does not include Corepack. The Tasks bootstrap exactly
`pnpm@10.4.1` into the shared workspace before running package scripts.
## Secret Contract ## Secret Contract
Infisical project `8520b8c0-3796-4fd6-a03c-6f0508c8c42c`, environment Infisical project `8520b8c0-3796-4fd6-a03c-6f0508c8c42c`, environment
@@ -129,6 +132,18 @@ The source test/build Tasks do not receive Gitea, Harbor, or Cloudflare
credentials. Credential Secrets are mounted only into the Tasks that require credentials. Credential Secrets are mounted only into the Tasks that require
them. them.
## External Setup
- Create the Infisical path and all six keys in the Secret Contract before the
first run.
- Point public DNS for `tekton-hook.dahyeon.us` to the same public ingress
endpoint as `tekton.dahyeon.us`.
- In Gitea, add an active push webhook for
`https://tekton-hook.dahyeon.us` with JSON content type and use the exact
`GITEA_WEBHOOK_SECRET` value as its signing secret.
- Protect `https://tekton.dahyeon.us` with an authentication layer such as
Cloudflare Access when build metadata and logs must not be public.
## Pipeline Contract ## Pipeline Contract
- Trigger: signed Gitea push event for exactly - Trigger: signed Gitea push event for exactly