Enterprise
Redis Configuration
NetBox uses Redis for caching and as a task queue for background workers. The operator supports two modes:
- Internal (default): Managed by the Redis Operator, installed as a chart dependency
- External: Connect to an existing Redis instance
Internal Redis (Default)
When redis.external: false (the default), the operator deploys a Redis cluster managed by the Redis Operator.
| Key | Type | Default | Description |
|---|---|---|---|
redis.external | bool | false | Use internal Redis |
redis.name | string | redis | Redis instance name |
redis.clusterSize | uint8 | 1 | Number of Redis replicas (0–255) |
redis.persistence | bool | true | Enable data persistence |
redis.requireAuth | bool | false | Require authentication |
redis.resources.cpu | int | 250 | CPU request in millicores |
redis.resources.memory | int | 256 | Memory request in MiB |
redis.storageClassName | string | — | Storage class for Redis PVCs |
Example with redundancy:
netboxEnterprise:
spec:
redis:
external: false
clusterSize: 3
persistence: true
External Redis
Set redis.external: true to use an externally managed Redis instance.
When external, provide connection details through netbox.config.redis:
netboxEnterprise:
spec:
redis:
external: true
netbox:
config:
redis:
host: "redis.example.com"
port: 6379
username: "netbox" # Optional, Redis 6.0+ ACL
password:
name: redis-credentials
key: password
You can disable the Redis Operator entirely:
redis-operator:
enabled: false
TLS Configuration
Configure TLS for connections to external Redis:
| Key | Type | Default | Description |
|---|---|---|---|
redis.tlsConfig.insecureSkipVerify | bool | false | Skip TLS verification (dev only) |
redis.tlsConfig.keychainCaCertificates | list | — | CA certificate names from tlsKeychain |
redis.tlsConfig.keychainClientCertificate | string | — | Client certificate name from tlsKeychain |
Example with TLS
netboxEnterprise:
spec:
redis:
external: true
tlsConfig:
keychainCaCertificates:
- my-redis-ca
tlsKeychain:
caCertificateSecrets:
- name: my-redis-ca
secret: redis-ca-cert
key: ca.crt
Redis Database Allocation
NetBox and Diode use separate Redis databases within the same instance:
| Database | Purpose |
|---|---|
0 | Diode reconciler |
1 | Diode ingester streams |
| Default | NetBox caching and task queue |
These database numbers are configurable in the Diode configuration section.
Next Steps
- Diode — Data ingestion pipeline that uses Redis streams
- PostgreSQL — Database configuration