Skip to content

Redis Insight

Web UI for Redis, deployed per environment as a plain Deployment + Service + Ingress (no Helm chart). Each environment points at its own Redis instance (see Redis).

Argo CD Application

k8s/envs/<env>/redis-insight/application.yaml references the same Git repo and applies the manifest directly:

source:
  repoURL: https://github.com/tomoda-labs/devops.git
  path: k8s/envs/<env>/redis-insight
  directory:
    recurse: true
    include: 'manifests.yaml'
destination:
  namespace: data

The directory.include: 'manifests.yaml' filter keeps Argo from picking up the application.yaml itself as a child resource. Both envs land in the data namespace.

Manifest

manifests.yaml (one per env) is three small resources:

  • Deployment: image redis/redisinsight:3.8.0, single replica, container port 5540, resources 50m–200m CPU and 128Mi–256Mi memory.
  • Service: ClusterIP, port 80 → targetPort 5540.
  • Ingress: Traefik class, TLS via cert-manager, oauth2-proxy middlewares.

Resources are named redisinsight-dev / redisinsight-prod, since both envs share the data namespace.

Ingress and auth

Same pattern as pgAdmin: the Ingress chains the sys-oauth2-proxy-errors and sys-oauth2-proxy-auth Traefik middlewares so every request is gated by oauth2-proxy + Google sign-in. The /oauth2 path routes to oauth2-proxy-redir for the callback. TLS certificates are stored in redisinsight-dev-tls (dev) / redisinsight-prod-tls (prod).

Env Host Stored as
dev redis-dev.tomoda.life redisinsight-dev-tls
prod redis-prod.tomoda.life redisinsight-prod-tls

Connecting to Redis

Redis Insight does not pre-register a connection; the operator adds one on first login. Use the in-cluster hostnames from the Redis page:

Env Host Port
dev redis-dev-master.data.svc.cluster.local 6379
prod redis-prod-master.data.svc.cluster.local 6379

Both Redis releases require a password: read it from GSM tomoda-redis-password-<env>.

Operations

  • Image bump: the tag is pinned in k8s/envs/{dev,prod}/redis-insight/manifests.yaml; change both together.
  • Reset: kubectl -n data rollout restart deploy/redisinsight-dev (or redisinsight-prod). Saved connections live in an ephemeral volume and are lost on restart; re-add the in-cluster host.
  • Local-only access: kubectl -n data port-forward svc/redisinsight-dev 8080:80 bypasses oauth2-proxy.