fix(k8s): remove stale GITEA_ACCESS_TOKEN/GITEA_API_URL/QDRANT_URL from k8s config

These env vars are no longer read by the application — all runtime
settings are managed through the Admin Dashboard Web UI backed by
SQLite. Only PORT remains in the ConfigMap. Secret resource removed
entirely. README k8s sections updated accordingly.
This commit is contained in:
jeffusion
2026-03-05 14:08:28 +08:00
committed by 路遥知码力
parent 7ef35fa8ee
commit 9b063afba0
3 changed files with 12 additions and 52 deletions

View File

@@ -183,23 +183,13 @@ docker-compose up -d
Kubernetes manifests are located in the `k8s/` directory.
**1. Configure Secrets**
**1. Configure**
Only the Gitea access token needs to be in the Secret (the only sensitive env-var-level setting):
The only env var in the ConfigMap is `PORT`. All other settings (Gitea connection, webhook secret, admin password, review engine, Feishu, etc.) are configured through the **Admin Dashboard Web UI** after deployment — they are auto-seeded with secure defaults on first boot.
```bash
echo -n "your_gitea_token" | base64
```
Ensure persistent storage is configured for the `/app/data` directory to retain the SQLite database and encryption key.
Update `GITEA_ACCESS_TOKEN` in `k8s/gitea-assistant.yaml`.
**2. Configure Application**
Edit the ConfigMap in `k8s/gitea-assistant.yaml`:
- Set `GITEA_API_URL` to your Gitea instance API endpoint
> **Note**: All other settings (webhook secret, admin password, review engine, Feishu, etc.) are configured through the Admin Dashboard Web UI after deployment. They are auto-seeded on first boot. Ensure persistent storage is configured for the `/app/data` directory.
**2. Deploy**
**3. Deploy**
```bash