RedisInstance

Scope: namespaced · Backend: OT-Container-Kit Redis operator (type: ot-container-kit)

Redis for Langfuse's cache and queue. Same type × mode shape as the other datastores.

Spec

Field	Type	Description
type	enum ot-container-kit	Backend implementation
mode	enum managed | adopt | external (required)	Provenance mode
managed	object	Storage, resources, replicas when mode: managed
adopt	object	Reference to an existing in-cluster Redis CR
external	object	Connection secret for an external Redis

adopt

Field	Description
instanceRef	The existing Redis CR. namespace is optional and may point at another namespace — the service host is built from it
passwordSecretRef	The Secret holding the password (key defaults to password). namespace defaults to the instance's namespace. Omit for an auth-less Redis

Behavior by mode

• managed — ensures the Redis operator (redis-operator) and creates its Redis custom resource (redis.redis.opstreelabs.in/v1beta2). The operator-generated password is stored as an owned Secret and is rotatable when the credential-rotation feature is licensed.
• adopt — references an existing in-cluster Redis CR — possibly in another namespace (cross-namespace adoption) — and normalizes its password into an owned <name>-adopted-credentials Secret in this namespace (canonical keys host / port / password / url) so consumers can wire to it. Lifecycle is not managed.
• external — wires a connection secret; no operator installed.

Langfuse can manage Redis for you

As with ClickHouse, the langfuse-operator can manage Redis internally. Unless the referenced datastore is external, Observability defaults to operator-managed Redis, making a dedicated RedisInstance optional.

Example — managed

apiVersion: core.navique.com/v1alpha1
kind: RedisInstance
metadata:
  name: forge-redis
  namespace: forge-data
spec:
  type: ot-container-kit
  mode: managed

Status

Exposes connection coordinates and the standard conditions and observedGeneration.