chore: LOG_LEVEL info in renovate, document secret management in README

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-05-20 13:58:58 +00:00
parent 71437e8932
commit e2d0173e43
2 changed files with 17 additions and 1 deletions
+16
View File
@@ -62,6 +62,22 @@ Instalar con:
cp .githooks/pre-commit .git/hooks/pre-commit
chmod +x .git/hooks/pre-commit
```
## Renovate Bot
Secret `renovate-token` gestionado manualmente (no está en el repo).
Para recrearlo:
```bash
kubectl create secret generic renovate-token \
--from-literal=RENOVATE_TOKEN=<token-gitea> \
-n renovate
```
Token en https://git.chemavx.xyz/user/settings/applications con permisos:
`issue`: Read/Write, `repository`: Read/Write, `user`: Read
Imagen fijada a `38.0.0` — no actualizar a `latest` sin probar autenticación primero.
## ArgoCD patches
Después de instalar ArgoCD aplicar:
`kubectl apply -f argocd-patches/redis-patch.yaml`
+1 -1
View File
@@ -27,7 +27,7 @@ spec:
- name: RENOVATE_CONFIG_FILE
value: /opt/renovate/config.js
- name: LOG_LEVEL
value: debug
value: info
resources:
requests:
cpu: 100m