unkinben
ee76ec199b
## Summary
- Deploys Kanidm 1.10.3 (ghcr.io/kanidm/server:1.10.3) as a 2-replica
StatefulSet with built-in replication enabled
- Domain: auth.unkin.net (primary WebAuthn origin); au.auth.unkin.net
is an additional hostname for this au-syd1 instance
- TLS: cert-manager Certificate (vault-issuer) covering auth.unkin.net,
au.auth.unkin.net, kanidm.k8s.syd1.au.unkin.net, and internal
headless pod DNS names — Kanidm terminates TLS itself (passthrough)
- Gateway: TLS passthrough on port 443 via TLSRoute; HTTP on port 80
redirects to HTTPS; external-dns creates kanidm.k8s.syd1.au.unkin.net
(not used in server.toml; canonical origin is auth.unkin.net only)
- Replication: init container generates per-pod server.toml with the
correct repl:// origin (kanidm-{N}.kanidm-headless.kanidm.svc);
populate kanidm-repl-peers ConfigMap post-deployment after running
`kanidmd show-replication-certificate` on each pod
- Storage: 10Gi cephrbd-fast-delete PVC per pod via volumeClaimTemplates
- Security: runAsUser/runAsGroup 1000, runAsNonRoot, no privilege
escalation, allowPrivilegeEscalation=false
- ArgoCD: platform ApplicationSet and Project updated for kanidm namespace
## Requires
- PR benvin/kanidm-artifactapi (add ^kanidm/ to ghcr immutable patterns)
to be merged first so artifactapi can cache ghcr.io/kanidm/server
## Post-deployment steps
1. Wait for both pods to reach Running state
2. Exchange replication certificates between pods:
kubectl exec -n kanidm kanidm-0 -- kanidmd show-replication-certificate
kubectl exec -n kanidm kanidm-1 -- kanidmd show-replication-certificate
3. Edit kanidm-repl-peers ConfigMap with both nodes' certs
(see template in configmap.yaml comments)
4. kubectl rollout restart statefulset/kanidm -n kanidm
## Test plan
- [x] Sandbox tested in sandbox-kanidm: all 11 resources server dry-run OK
- [ ] After merge: ArgoCD syncs kanidm namespace
- [ ] Verify auth.unkin.net and au.auth.unkin.net reachable via Gateway
- [ ] Verify kanidm.k8s.syd1.au.unkin.net DNS record created by external-dns
- [ ] Complete replication cert exchange and verify replication active
58 lines
1.5 KiB
YAML
58 lines
1.5 KiB
YAML
---
|
|
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: kanidm-config
|
|
namespace: kanidm
|
|
labels:
|
|
app.kubernetes.io/name: kanidm
|
|
app.kubernetes.io/instance: kanidm
|
|
data:
|
|
server.toml: |
|
|
version = "2"
|
|
|
|
domain = "auth.unkin.net"
|
|
origin = "https://auth.unkin.net"
|
|
bindaddress = "[::]:8443"
|
|
db_path = "/data/kanidm.db"
|
|
db_arc_size = 2048
|
|
tls_chain = "/data/tls/tls.crt"
|
|
tls_key = "/data/tls/tls.key"
|
|
log_level = "info"
|
|
|
|
[online_backup]
|
|
path = "/data/backups/"
|
|
schedule = "0 22 * * *"
|
|
versions = 7
|
|
|
|
[replication]
|
|
origin = "__REPL_ORIGIN__"
|
|
bindaddress = "[::]:8444"
|
|
---
|
|
# kanidm-repl-peers is initially empty.
|
|
#
|
|
# After first deployment, exchange replication certificates:
|
|
# kubectl exec -n kanidm kanidm-0 -- kanidmd show-replication-certificate
|
|
# kubectl exec -n kanidm kanidm-1 -- kanidmd show-replication-certificate
|
|
#
|
|
# Then populate peers.toml with both nodes' certs and restart pods.
|
|
# Example peers.toml content:
|
|
#
|
|
# [replication."repl://kanidm-0.kanidm-headless.kanidm.svc.cluster.local:8444"]
|
|
# type = "mutual-pull"
|
|
# partner_cert = "<base64-cert-from-kanidm-0>"
|
|
#
|
|
# [replication."repl://kanidm-1.kanidm-headless.kanidm.svc.cluster.local:8444"]
|
|
# type = "mutual-pull"
|
|
# partner_cert = "<base64-cert-from-kanidm-1>"
|
|
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: kanidm-repl-peers
|
|
namespace: kanidm
|
|
labels:
|
|
app.kubernetes.io/name: kanidm
|
|
app.kubernetes.io/instance: kanidm
|
|
data:
|
|
peers.toml: ""
|