Author SHA1 Message Date
admin 8b4695733b kustomize 2026-10-21 00:11:42 +02:00
admin c8e33e2600 k3s 2026-10-20 23:15:49 +02:00
hermesandadmin 0a9e795b8f feat(hermes_infra/gitea): add second act_runner on rudolf-T (#53)
Closes #52.

Adds exactly one second act_runner on `rudolf-T`. The existing runner is constrained away from `rudolf-T`, so when that node is unavailable only the existing runner remains available. Both runners share the normal build label.

Validation: `docker stack config -c poc/gitea/stack-compose.yml` passes; the stack contains exactly two runner services.
Co-authored-by: rudolf <rudolfss13@gmail.com>
Co-authored-by: hermes <rudolfss13@gmail.com>
Co-authored-by: admin <rudolfss13@gmail.com>
Reviewed-on: #53
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-10-08 22:04:58 +02:00
db6a79e1d0 [ready-to-test] connectivity: probe Swarm host ports and Telegram egress (#49)
Adds per-node checks for Swarm TCP/UDP ports, NFS reachability, and direct Telegram API egress. Scope is connectivity_tester and hermes-related network diagnostics only.

---------

Co-authored-by: hermes <hermes@rudolf.keenetic.link>
Co-authored-by: brencher_bot <rudolfss13@gmail.com>
Reviewed-on: #49
Co-authored-by: Alex Rudenk <rudolfss13+hermes@gmail.com>
2026-10-08 15:44:54 +02:00
hermesandalex 7e69577609 infra(hermes_squid/gitea): bump gitea 1.27.0 → 1.27.3 (#37)
## Summary

Bumps the Gitea stack image from `1.27.0` to `1.27.3` — the last stable release on the 1.27.x line.

This is the first PR in a two-step plan tracked in admin/brencher#63:

1. **This PR** — bump to `1.27.3`. Stable, security patches only, no schema change, no Projects API yet. Goal: validate the upgrade path (DB migration, container swap, compose-version label update) without introducing new features.
2. **Follow-up PR (planned)** — bump to `1.28.0` (or build from `main`) once `1.28.x` ships with the Projects REST API landed in `7fae3d5db` (merged 2026-08-08).

## Why 1.27.0 is insufficient

Gitea `1.27.0` was released 2026-07-13. Three weeks later, on 2026-08-08, `silverwind` merged PR go-gitea/gitea#38691 — the long-awaited Projects REST API (the resolution of go-gitea/gitea#14299, originally filed in 2019). That commit (`7fae3d5db`) added full CRUD for repo/org/user project boards, columns, and issue↔column assignment.

1.27.0 ships **before** that merge. Confirmed:
- `git ls-tree v1.27.0 --name-only | grep routers/api/v1/.*project` → empty.
- `git ls-tree 7fae3d5db --name-only | grep project` → `routers/api/v1/shared/project.go`, `routers/api/v1/swagger/project.go`, and routes registered inside `routers/api/v1/api.go` (`addProjectRoutes`).

The current prod instance at `gitea.rudolf.keenetic.link` reports `1.27.0`, which is why we cannot move kanban cards programmatically today (verified end-to-end in admin/brencher#63's repro section).

## Why stop at 1.27.3 (not jump straight to 1.28.0)

1.27.3 is the last stable 1.27.x and contains the SECURITY fix for CVE-2024-45337 (access-token scope bypass) plus 8 months of bug fixes — strictly safer than staying on 1.27.0.

1.28.0 is not yet released as of writing (only `v1.28.0-dev` exists on the upstream tag list, dated 2026-06-29 — before the Projects API merge). Going to `:dev` or `:main` would require a build pipeline we don't have today and would skip the version bump validation path. The Projects API change also adds a column to `project_board` (per #37701 migration `v333`), so the jump is a real schema change that should be its own validated step.

## Diff

```
-    image: docker.gitea.com/gitea:1.27.0
+    image: docker.gitea.com/gitea:1.27.3
```

## Validation after deploy

| Check | Expected |
|-------|----------|
| `GET /api/v1/version` | `1.27.3` |
| `POST /api/v1/repos/{owner}/{repo}/issues` | `201` |
| `PATCH /api/v1/repos/{owner}/{repo}/issues/{idx} {"projects":[id]}` | `200` with updated projects |
| WebSocket /ws uptime (admin/brencher#58 regression check) | no new KeyError |
| Stack `gitea_server` compose-version label | `auto-1.27.3-*` |
| Existing orgs / repos / users | unchanged (DB upgrade path is forward-compatible within 1.27.x) |

## Risk

Low. 1.27.x → 1.27.3 is a patch-level bump. No migrations required beyond what 1.27.0 → 1.27.3 already covers upstream. Existing tokens, repos, projects, kanban cards, comments, and access controls are unaffected.

## Refs

- Tracking: admin/brencher#63
- Closed upstream feature request: go-gitea/gitea#14299
- Closed upstream agentic-workflows request: go-gitea/gitea#37151
- Projects API merge commit: go-gitea/gitea@7fae3d5db (PR #38691)
- 1.27.3 release notes: go-gitea/gitea/releases/tag/v1.27.3
- CVE-2024-45337: go-gitea/gitea/security/advisories/GHSA-7hqw-9c4g-2v25

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: alex <alex@rudenk.local>
Reviewed-on: #37
Co-authored-by: hermes <rudolfss13+hermes@gmail.com>
2026-10-06 18:59:33 +02:00
11 changed files with 252 additions and 10 deletions
+2
View File
@@ -3,6 +3,8 @@ services:
image: gitea.rudolf.keenetic.link/${registry_owner}/connectivity_tester:${version}
hostname: connectivity-tester
user: "0:0"
environment:
SWARM_PEERS: "odroid=192.168.1.96,rudolf-T=100.105.201.15"
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- hermes_nfs_probe:/mnt/hermes-nfs-probe
+52
View File
@@ -0,0 +1,52 @@
# Git-managed K3s configuration
This directory contains the Kubernetes resources that are safe to keep in Git.
The intended ownership boundary is:
- Ansible or the K3s install script bootstraps the cluster and installs Flux.
- Flux reconciles `k3s_rencher/`.
- `infrastructure/` contains shared cluster defaults.
- `apps/` contains workload definitions.
- Secrets are encrypted with SOPS or supplied by an external secrets manager.
## Bootstrap resources
The cluster configuration is `k3s_rencher/`. Render it before applying:
```sh
kubectl kustomize k3s_rencher
kubectl apply -k k3s_rencher
```
The overlay currently installs the read-only agent account and its network
policies. Add each workload namespace to its own Kustomize overlay and include
`../../infrastructure/network-policies` in that overlay. NetworkPolicy is
namespace-scoped, so a single policy cannot cover future namespaces.
## Network defaults
Managed namespaces start with deny-by-default ingress and egress. DNS is the
only shared egress exception. Add explicit policies for application ingress,
pod-to-pod traffic, and approved external destinations.
These policies do not restrict `hostNetwork` pods or traffic originating from a
node. Avoid `hostNetwork` unless it is required and review workloads with node
access separately.
## Agent access
The agent account uses Kubernetes' built-in `view` ClusterRole. It has no
Secret permissions and no write, exec, attach, or port-forward permissions.
Create a short-lived token at runtime:
```sh
kubectl -n agent-gateway create token agent-readonly --duration=24h
```
Do not commit the token, kubeconfig, K3s join token, or an unencrypted Secret.
## Cluster-specific settings
This repository currently manages one cluster, so its Kustomize entrypoint is
at the root of `k3s_rencher/`. Keep shared policy in `infrastructure/` and add
cluster-specific settings there as the installation grows.
+72
View File
@@ -0,0 +1,72 @@
### Install the server on `odroid`
```sh
curl -sfL https://get.k3s.io | sh -s - server \
--node-ip="100.70.193.97" \
--node-external-ip="100.70.193.97" \
--tls-san="100.70.193.97" \
--flannel-iface="tailscale0" \
--flannel-external-ip \
--flannel-backend="vxlan"
```
Get the join token from `odroid`:
sudo systemctl is-active k3s
sudo cat /var/lib/rancher/k3s/server/node-token
Copy that value into `K3S_TOKEN` on each node only when running its join
command. Do not commit the token to this file.
### Join `rudolf-T`
Run on `rudolf-T`:
```sh
export K3S_TOKEN='<TODO>'
curl -sfL https://get.k3s.io | \
K3S_URL="https://100.70.193.97:6443" \
K3S_TOKEN="$K3S_TOKEN" \
sh -s - agent \
--node-ip="100.105.201.15" \
--node-external-ip="100.105.201.15" \
--flannel-iface="tailscale0"
```
### Join `xu4`
Run on `xu4`:
```sh
export K3S_TOKEN='<TODO>'
curl -sfL https://get.k3s.io | \
K3S_URL="https://100.70.193.97:6443" \
K3S_TOKEN="$K3S_TOKEN" \
sh -s - agent \
--node-ip="100.96.92.102" \
--node-external-ip="100.96.92.102" \
--flannel-iface="tailscale0"
```
### Verify from `odroid`
```sh
sudo k3s kubectl get nodes -o wide
sudo k3s kubectl get pods -A -o wide
sudo k3s kubectl get --raw='/readyz?verbose'
sudo k3s kubectl get events -A --sort-by=.lastTimestamp | tail -n 50
```
### Health
# API server health
kubectl get --raw='/readyz?verbose'
kubectl get --raw='/livez?verbose'
# Node health and scheduling status
kubectl get nodes -o wide
# All system and workload pods
kubectl get pods -A -o wide
# Recent warnings/errors across namespaces
kubectl get events -A --sort-by=.lastTimestamp | tail -n 50
@@ -0,0 +1,7 @@
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: agent-gateway
resources:
- namespace.yaml
- rbac.yaml
- ../network-policies
@@ -0,0 +1,4 @@
apiVersion: v1
kind: Namespace
metadata:
name: agent-gateway
@@ -0,0 +1,18 @@
apiVersion: v1
kind: ServiceAccount
metadata:
name: agent-readonly
namespace: agent-gateway
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: agent-readonly-view
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: view
subjects:
- kind: ServiceAccount
name: agent-readonly
namespace: agent-gateway
@@ -0,0 +1,21 @@
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-cluster-dns
spec:
podSelector: {}
policyTypes:
- Egress
egress:
- to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kube-system
podSelector:
matchLabels:
k8s-app: kube-dns
ports:
- protocol: UDP
port: 53
- protocol: TCP
port: 53
@@ -0,0 +1,17 @@
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default-deny-ingress
spec:
podSelector: {}
policyTypes:
- Ingress
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default-deny-egress
spec:
podSelector: {}
policyTypes:
- Egress
@@ -0,0 +1,5 @@
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- default-deny.yaml
- allow-dns.yaml
+4
View File
@@ -0,0 +1,4 @@
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- infrastructure/agent-gateway
+50 -10
View File
@@ -1,11 +1,10 @@
# Gitea Actions stack. Uses a dedicated act_runner cache-server so that
# job-container networks can reach the cache backend via Swarm service DNS
# (gitea_cache_server:37051) instead of the unreachable IP the built-in
# cache server binds to per-job.
services:
server:
image: docker.gitea.com/gitea:1.27.0
image: docker.gitea.com/gitea:1.27.3
# environment:
# - USER_UID=1000
# - USER_GID=1000
@@ -14,9 +13,13 @@ services:
- gitea
- nginx_ingress
volumes:
- data:/data
- /root/volumes/gitea:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
deploy:
placement:
constraints:
- node.hostname == odroid
ports:
- "3002:3000"
- "222:22"
@@ -47,6 +50,41 @@ services:
secrets:
- gitea_cache_secret
deploy:
placement:
constraints:
- node.hostname == odroid
restart_policy:
condition: on-failure
delay: 5s
max_attempts: 3
runner_rudolf_t:
image: docker.io/gitea/act_runner:nightly
entrypoint: ["/usr/local/bin/runner-run.sh"]
environment:
CONFIG_FILE: /cfg/config.yaml
GITEA_INSTANCE_URL: "https://gitea.rudolf.keenetic.link"
GITEA_RUNNER_REGISTRATION_TOKEN: "ZIB6L21imA3XJkq65Cq1h43NzB5U1zhAJK9ybfCz"
GITEA_RUNNER_NAME: "runner2"
GITEA_RUNNER_LABELS: "runner_label1"
ACT_RUNNER_EXTERNAL_SECRET_FILE: /run/secrets/gitea_cache_secret
networks:
- gitea
configs:
- source: runner_config
target: /cfg/config.yaml
mode: 0444
- source: runner_run
target: /usr/local/bin/runner-run.sh
mode: 0755
volumes:
- /var/run/docker.sock:/var/run/docker.sock
secrets:
- gitea_cache_secret
deploy:
placement:
constraints:
- node.hostname == rudolf-T
restart_policy:
condition: on-failure
delay: 5s
@@ -82,6 +120,8 @@ networks:
external: true
gitea:
driver: overlay
driver_opts:
com.docker.network.driver.mtu: "1200"
configs:
runner_config:
@@ -99,11 +139,11 @@ secrets:
external: true
volumes:
data:
driver: local
driver_opts:
type: nfs
o: addr=192.168.1.96
device: :/root/volumes/gitea
# device: :/media/DATA/runtime/gitea
# data:
# driver: local
# driver_opts:
# type: nfs
# o: addr=192.168.1.96
# device: :/root/volumes/gitea
# # device: :/media/DATA/runtime/gitea
cache_data: