Mukul SharmaandClaude Opus 5
f83cedca65
Ports the rest of the homelab's stack: external-secrets, harbor, jenkins, postgresql, redis, victoria-metrics-single, vmagent, node-exporter and grafana. All nine verified with helm template. Most are the homelab's values with storage moved from local-path to standard-rwo and hostnames rebuilt on the reserved ingress IP. vmagent and node-exporter are unchanged outright — everything in them is addressed by cluster DNS, namespace or container port, none of which differs here. Harbor is the substantial one. The homelab serves it over plain HTTP and makes containerd accept that by hand-editing hosts.toml on the node; GKE nodes are managed and replaced, so that edit cannot survive. Instead the node pool was told at creation to trust a private CA for exactly this hostname, and cert-manager now signs Harbor's certificate from that same CA via an ingress-shim annotation. certSource is "secret" rather than the chart's "auto", which would self-sign a certificate nothing trusts. externalURL moves to https to match, since Harbor hands that URL to docker clients and a mismatch surfaces as registry errors. Jenkins drops secondaryingress, which exists in the homelab only to serve its Tailscale hostname. Its plugin pins are carried over deliberately: each fixes a failure whose symptom points somewhere else, above all the kubernetes/kubernetes-client-api pairing, without which agents never come online and builds hang at "Still waiting to schedule task". Postgres and Redis keep the homelab's deliberately small memory settings. Those were chosen for an 8GB node under pressure, and while this cluster has room, a bigger cache buys nothing for a handful of small tools. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LEsTefWWifp4ikvhHF5s6N
46 lines
1.3 KiB
YAML
46 lines
1.3 KiB
YAML
# PostgreSQL for toolshed's control plane, on GKE.
|
|
#
|
|
# Its own namespace rather than toolshed's, so it is addressed over cluster
|
|
# DNS like any other platform component and outlives its first consumer:
|
|
#
|
|
# postgresql.postgres.svc.cluster.local:5432
|
|
#
|
|
# Hand-written chart, not Bitnami's: that registry has been unstable, and
|
|
# PostgreSQL ships no official chart.
|
|
#
|
|
# Credentials come from Vault through External Secrets — see
|
|
# secretstores/toolshed-postgres-credentials.yaml. The Secret must exist
|
|
# before this pod starts; without it the pod sits in
|
|
# CreateContainerConfigError, which does not explain itself.
|
|
|
|
fullnameOverride: postgresql
|
|
|
|
image:
|
|
repository: postgres
|
|
tag: "16-alpine"
|
|
pullPolicy: IfNotPresent
|
|
|
|
existingSecret: postgresql-credentials
|
|
database: toolshed
|
|
|
|
persistence:
|
|
enabled: true
|
|
storageClass: standard-rwo
|
|
size: 5Gi
|
|
|
|
config:
|
|
# Kept at the homelab's deliberately small values even though this
|
|
# cluster has room to spare: for a handful of control-plane tables it
|
|
# makes no measurable difference, and matching the homelab keeps one
|
|
# fewer variable between the two deployments. Raise it if a real query
|
|
# workload ever shows up here.
|
|
sharedBuffers: 32MB
|
|
maxConnections: "50"
|
|
|
|
resources:
|
|
requests:
|
|
cpu: 50m
|
|
memory: 64Mi
|
|
limits:
|
|
memory: 256Mi
|