Nik Afiq
28d062801a
The previous ip6tables->sysctl fix (26894d1) was itself wrong: writing /proc/sys/net/ipv6/conf/all/disable_ipv6 failed live with "Read-only file system" despite NET_ADMIN and a passing [ -w ] check - the container runtime mounts /proc/sys read-only by default regardless of capabilities, independent of file permission bits. Making it writable needs either kubelet's securityContext.sysctls (and net.ipv6.conf.*.disable_ipv6 isn't on its default safe-sysctls allowlist, so that means a node-level --allowed-unsafe-sysctls flag) or securityContext.procMount: Unmasked (which needs pod-level user namespaces) - too much blast radius for one pod's IPv6 kill switch. nft (nftables) is genuinely present in the same image (the "nftables" apk package, installed alongside "iptables" but not "ip6tables") and handles the ip6 address family without a separate binary, so it needs no image or capability change. Verified by actually running the exact commands against the real pinned nicolaka/netshoot:v0.11 image (digest-matched to what's on nik-debian), not just against docs. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Kubernetes Manifests
This directory contains raw Kubernetes resources grouped by service area. Most
subdirectories are consumed by Argo CD Applications in argocd/apps.
Directories
| Directory | Contents |
|---|---|
argocd/ |
App-of-apps, Argo CD ingress, Argo CD OIDC sealed secret |
authentik/ |
Authentik ingress, public ingress, proxy outpost, middleware, secret scripts |
cert-manager/ |
Internal and Let's Encrypt ClusterIssuers, Porkbun secret script |
core/ |
Dashy, Glances, CoreDNS custom config, CA installer |
gitea/ |
Gitea storage, backup, public ingress, runner and OIDC/admin secrets |
home-services/ |
HA gateway, AI gateway, Discord bot, service TLS, registry secret |
homeassistant/ |
Home Assistant external service and ingress |
media/ |
Jellyfin, qBittorrent, JDownloader (sending links) |
monitoring/ |
Monitoring PVs, Grafana datasource, Grafana/Auth OIDC secrets |
network/ |
Pi-hole secrets, DDNS, Traefik dashboard, external host ingresses |
portfolio/ |
Portfolio deployment, ingress, registry pull secret |
Secrets
There are two patterns:
*-sealed.yamlfiles are safe to commit and are reconciled by Sealed Secrets.*.shscripts create runtime Secrets from.envdirectly in the cluster.
Use .env.example as the template for local secret names. kubeseal must point
at the in-cluster controller named sealed-secrets-controller in kube-system.
Regenerate committed sealed secrets with the matching script, then commit the resulting YAML. Runtime secret scripts should be run against the target cluster and should not produce committed plaintext.
Certificates
Internal services generally use internal-ca-issuer and home.arpa hostnames.
Public services use Let's Encrypt issuers and nik4nao.com hostnames.
The CA installer lives in core/ca-installer. Its ca-sync CronJob keeps the
served ca.crt and Apple mobileconfig in sync with the cert-manager CA secret.
DNS
Internal DNS records are configured in values/pihole.yaml and
values/pihole-debian.yaml. Add a new hostname to both files when adding a
home.arpa service.
Dashy
core/dashy.yaml defines the deployment and a placeholder ConfigMap. The real
dashboard config comes from config/dashy/conf.yaml:
bash manifests/core/apply-dashy-config.sh