roger/k3s-cluster
1
0
Fork 1
Code Issues Pull Requests 6 Actions Packages Projects Releases Wiki Activity

Compare commits

base: roger:fix/myorg-git-sync-clone
Branches Tags
roger:main roger:fix/homeassistant-memory roger:fix/homeassistant-pin-version roger:fix/litellm-memory-limits roger:fix/gitsync-host-normalize roger:fix/myorg-git-sync-clone
..
compare: roger:e44d7ba1fcefc4ceb8f31c145c46cff277861f72
Branches Tags
roger:main roger:fix/homeassistant-memory roger:fix/homeassistant-pin-version roger:fix/litellm-memory-limits roger:fix/gitsync-host-normalize roger:fix/myorg-git-sync-clone

5 Commits
fix/myorg- ... e44d7ba1fc

Author SHA1 Message Date
Roger Oriol
e44d7ba1fc Merge branch 'main' of https://git.rogi.casa/roger/k3s-cluster 2026-07-19 12:01:21 +02:00
Roger Oriol
f1005cd426 change openwebui url to ai.rogi.casa 2026-07-19 12:00:52 +02:00
Roger Oriol
43c0c2561e fix hermes write folder 2026-07-18 19:29:52 +02:00
roger
8334cd48f8 Merge pull request 'fix(myorg-assistant): add git-clone initContainer to git-sync CronJob' (#26) from fix/myorg-git-sync-clone into main 
Reviewed-on: #26
 2026-07-18 19:25:00 +02:00
Hermes Platform Engineer
ba7e05a73d fix(myorg-assistant): add git-clone initContainer to git-sync CronJob 
The git-sync CronJob only ran `git pull`/`git push` against /data/myorg
but never ensured the repo existed. The clone was solely the Deployment's
git-clone initContainer's job, and when that didn't populate the volume the
cron pod failed with 'Not a git repository: /data/myorg' on every run (and
swallowed the error, exiting 0).

Add an idempotent git-clone initContainer (guarded by [ ! -d /data/myorg/.git ])
so the cron job self-heals and actually syncs.

Refs: myorg-git-sync-* 'Pull: Error: Not a git repository' (last 24h+)
 2026-07-18 17:21:26 +00:00
3 changed files with 10 additions and 7 deletions
Expand all files Collapse all files

6
myorg-assistant/cronjobs/git-sync.yaml
View File

@@ -31,12 +31,8 @@ spec:
- sh - sh
- -c - -c
- | - |
# Normalize the repo URL host to the correct Gitea subdomain.
# The GIT_REPO_URL secret historically contained gitea.rogi.casa,
# which 526s through Cloudflare; the working subdomain is git.rogi.casa.
export GIT_REPO_URL="$(echo "${GIT_REPO_URL}" | sed -E 's#https?://[^/@]+@?gitea\.rogi\.casa#https://'"${GIT_USERNAME}"':'"${GIT_TOKEN}"'@git.rogi.casa#')"
if [ ! -d /data/myorg/.git ]; then if [ ! -d /data/myorg/.git ]; then
echo "Cloning repository from ${GIT_REPO_URL}..." echo "Cloning repository..."
git clone ${GIT_REPO_URL} /data/myorg git clone ${GIT_REPO_URL} /data/myorg
cd /data/myorg cd /data/myorg
git config user.name "${GIT_USERNAME}" git config user.name "${GIT_USERNAME}"

4
openwebui/ingress.yaml
View File

@@ -9,10 +9,10 @@ spec:
ingressClassName: traefik ingressClassName: traefik
tls: tls:
- hosts: - hosts:
- openai.rogi.casa - ai.rogi.casa
secretName: openwebui-tls secretName: openwebui-tls
rules: rules:
- host: openai.rogi.casa - host: ai.rogi.casa
http: http:
paths: paths:
- path: / - path: /

7
platform-engineer/deployment.yaml
View File

@@ -125,6 +125,13 @@ spec:
env: env:
- name: HERMES_HOME - name: HERMES_HOME
value: /opt/data value: /opt/data
# Hermes' file-write tool refuses any path outside HERMES_WRITE_SAFE_ROOT.
# When unset it defaults to HERMES_HOME (/opt/data), which blocks the
# agent's only GitOps remediation path (editing manifests under
# /workspace/k3s-cluster). Whitelist the whole filesystem — consistent
# with yolo:true, approvals.mode:off, and the agent having no k8s RBAC.
- name: HERMES_WRITE_SAFE_ROOT
value: "/"
volumeMounts: volumeMounts:
- name: data - name: data
mountPath: /opt/data mountPath: /opt/data