Files
argocd-apps/apps/base/logging/logviewer/service.yaml
T
unkin-agent 96e82a3584
ci/woodpecker/pr/vector-test Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline was successful
logging: deploy logviewer v0.1.0 behind oauth2-proxy
The logviewer UI gives browser access to the ClickHouse log store; it is
deployed behind an Authentik-gated oauth2-proxy front so only
akP-logviewer-admin members reach it, at https://logviewer.unkin.net.

- Adds the logviewer Deployment (docker-internal/logviewer:v0.1.0) reading
  ClickHouse via the existing clickhouse-logreader credentials
- Adds an oauth2-proxy front (quay.io v7.15.3) with ak_groups-based
  authorization, mirroring the arrstack pattern
- Syncs kv kubernetes/namespace/logging/default/oauth-credentials into the
  logviewer-oauth-credentials Secret via the existing default VaultAuth
- Adds internal Gateway + HTTPRoutes for logviewer.unkin.net (vault-issuer
  cert, external-dns -> 198.18.200.4, http->https redirect)
- Registers the logviewer directory in the logging kustomization
2026-08-23 17:31:36 +10:00

37 lines
691 B
YAML

---
apiVersion: v1
kind: Service
metadata:
name: logviewer
namespace: logging
spec:
internalTrafficPolicy: Cluster
ports:
- name: http
port: 8080
protocol: TCP
targetPort: http
selector:
app: logviewer
sessionAffinity: None
type: ClusterIP
---
# Front-door entry Service: the HTTPRoute for logviewer.unkin.net targets this;
# all traffic enters via oauth2-proxy.
apiVersion: v1
kind: Service
metadata:
name: logviewer-oauth2
namespace: logging
spec:
internalTrafficPolicy: Cluster
ports:
- name: http
port: 80
protocol: TCP
targetPort: http
selector:
app: logviewer-oauth2
sessionAffinity: None
type: ClusterIP