This page is sourced from the avvy/argocd repository (project id 150 at gitlab.avvyland.com). The repo's top-level directories enumerate every workload deployed via ArgoCD / Kustomize. If a service is not listed here, it is not running in the production Kubernetes cluster.
Cluster: Kubernetes on Hetzner Cloud (per common/hcloud-csi.yml, common/hcloud-volumes-immediate.yaml, and the Hetzner-specific networking in cloudflare/).
Namespaces seen in manifests: avvy-prod (workloads), avvy-dev / avvy-test (overlays), fdb-system (FoundationDB operator), cert-manager, kube-system, gitlab-runner.
avvy/argocd/state-server-all/base/deployment.yaml. Image gitlab.avvyland.com:5050/avvy/state-server:latest, container port 8443, replicas 1. Init container waits for fdb-cluster-file; runtime mounts state-server-secrets, state-server-config, tls-secret, fdb-cluster-file. Production runs against FoundationDB despite the code default of MongoDB. See state-server architecture.
avvy/argocd/avvy-worker/deployment.yaml. Image gitlab.avvyland.com:5050/avvy/avvy-worker:latest, namespace avvy-prod, replicas 1. Env includes REDIS_ADDRESS=redis:6379, MODEL_PREVIEW_QUEUE_NAME=model-previews, S3_ENDPOINT=https://fsn1.your-objectstorage.com, plus provider keys from the avvy-worker-secrets Kubernetes Secret (OpenAI, Tencent, etc.). See avvy-worker architecture.
avvy/argocd/avvyapp/deployment.yaml + avvyapp-all/base/. Image gitlab.avvyland.com:5050/avvy/avvy-app:latest, namespace avvy-prod, container port 9898, replicas 1. Ingress: app.avvyland.com with TLS via app.avvyland.com-tls. See avvy-app architecture.
avvy/argocd/webapp/deployment.yaml. Image gitlab.avvyland.com:5050/avvy/web-app-avvy:latest, namespace avvy-prod, container port 9898. Separate from avvyapp — this is the legacy web-app-avvy repo deployed as webapp.avvyland.com. Status / role versus avvyapp is not documented in current docs; treated as a deployed-but-secondary surface.
avvy/argocd/avvy-landing-all/base/deployment.yaml. Image gitlab.avvyland.com:5050/avvy/avvy-landing:latest, container port 80, replicas 1. The platform's landing site.
avvy/argocd/contask/deployment.yaml. Image gitlab.avvyland.com:5050/avvy/contask:latest, namespace avvy-prod, container port 9999. Ingress host: contask.avvyland.com. Repo description is sparse; deployed but role is not documented in the live state-server codebase. Source-of-truth gap — investigate before extending the wiki.
avvy/argocd/shopify-sync/. Deployed under sc.avvyland.com. Integrates Shopify product sync into the platform; the corresponding state-server endpoints are not present in the current handler tree, so the integration shape is not yet documented end-to-end. Source-of-truth gap.
avvy/argocd/content-processor/deployment.yaml. Image gitlab.avvyland.com:5050/avvy/content-processor:latest, namespace avvy-prod, name content-processor-worker, CPU request 4, memory request 6G. Asset processing worker. Its precise relationship to avvy-worker's preview / projection pipelines is not documented; treated as an independent processor.
avvy/argocd/texture-converter/deployment.yaml. Image gitlab.avvyland.com:5050/avvy/texture-convertor:latest123123 (note the suspect trailing tag — verify in production before relying on this image). Namespace avvy-prod, name texture-converter-worker, CPU 2, memory 2G. Texture-conversion worker; same integration-gap caveat as content-processor.
avvy/argocd/js-wiki/. Hosts this very wiki at wiki.avvyland.com.
avvy/argocd/outline/. Outline knowledge-base instance at docs.avvyland.com. Separate from this Wiki.js; complementary documentation surface.
avvy/argocd/foundationdb/base/fdb.yaml plus per-env overlays (avvy-dev, avvy-prod, avvy-test). Deployed via the FoundationDB Operator into fdb-system. state-server's init container waits for the operator-provided cluster file.
avvy/argocd/common/redis-deployment.yaml + redis-config / pvc / service. Reachable inside the cluster as redis:6379. Serves both as a cache for state-server and as the asynq task queue for avvy-worker.
External to the cluster. avvy-worker writes to https://fsn1.your-objectstorage.com (Hetzner Object Storage, bucket avvyland, region fsn1). Credentials live in avvy-worker-secrets.
avvy/argocd/cert-manager/cert-manager.yaml, cluster-issuer.yaml. TLS certificate issuance and renewal for every ingress.
avvy/argocd/cloudflare/deployment.yaml. Synchronises Kubernetes ingresses to Cloudflare DNS records.
avvy/argocd/autoscaler/deployment.yaml + hpa.yaml. Cluster + horizontal pod autoscaling.
avvy/argocd/gitlab-runner/. CI/CD runner for GitLab pipelines.
avvy/argocd/monitoring/. Prometheus + Grafana stack. Grafana is also the OTLP destination for avvy-worker traces — see Observability.
avvy/argocd/common/{ns.yaml, sysctl-inotify-daemonset.yaml, hcloud-csi.yml, hcloud-volumes-immediate.yaml, values.yaml}. Namespaces, Hetzner CSI driver, inotify tuning daemonset, shared values.
The first wiki pass listed architecture pages for repos that have no corresponding ArgoCD Application — most are dormant or obsolete. To preempt confusion:
auth_backend, avvy/storage, storage-workers, blocks-admin, avvy-storage, the entire blockchain family (avvy-l1/l2/l3/quorum-*/relayer/l1-wrapper/l2nodeipfs), the UCS family (ucs/ucs-unity-loader/ucs-wizard/uco-mappper-py), the ML services (content-processor is deployed but faiss-service / resnet-service / resnet-faiss-service / names-generator are not), the asset-pipeline GitLab repos that aren't content-processor or texture-converter, and unity-avvyland-core — none have ArgoCD manifests in this repo. Treat them as historical.
# Top-level deployments
curl -s --header "PRIVATE-TOKEN: <token>" \
"https://gitlab.avvyland.com/api/v4/projects/150/repository/tree?recursive=true&per_page=200" \
| jq -r '.[] | select(.type=="tree") | .path' \
| awk -F/ '{print $1}' | sort -u
# A specific manifest
curl -s --header "PRIVATE-TOKEN: <token>" \
"https://gitlab.avvyland.com/api/v4/projects/150/repository/files/<url-encoded-path>/raw?ref=main"
gitlab.avvyland.com/avvy/argocd — every .yaml manifest cited above. Verified at the time this page was authored.