{
  "schema_version": 2,
  "id": "operate/kubernetes/security/fips",
  "title": "Enable FIPS 140-3 compliance mode",
  "url": "https://redis.io/docs/latest/operate/kubernetes/8.2.0/security/fips/",
  "summary": "Run Redis Software for Kubernetes in FIPS 140-3 compliance mode.",
  "content": "\nYou can run your Redis Software for Kubernetes cluster in FIPS 140-3 compliance mode, which uses cryptographic libraries based on FIPS 140-3 validated modules and enables the use of FIPS-approved cryptographic algorithms. FIPS mode is available starting with operator version 8.2.0.\n\nWhen you enable FIPS mode, the operator deploys a FIPS-compatible image in place of the standard one.\n\n## Prerequisites\n\nFIPS compliance depends on the underlying platform, not only on Redis:\n\n- **FIPS-configured nodes.** A container runs in FIPS mode only if the host node is configured for FIPS. On OpenShift, the cluster must be installed in FIPS mode. Redis does not configure the host; this is the responsibility of your platform.\n- **amd64 architecture.** The FIPS-compatible Redis Software image is built for `amd64` only. There is no arm64 FIPS image.\n\n## Enable FIPS mode\n\nSet `spec.securityContext.fips.enabled` to `true` on the `RedisEnterpriseCluster` (REC):\n\n```yaml\napiVersion: app.redislabs.com/v1\nkind: RedisEnterpriseCluster\nmetadata:\n  name: rec\nspec:\n  securityContext:\n    fips:\n      enabled: true\n```\n\nWhen enabled, the operator adds a `.fips` suffix to the image version tag and pulls the matching FIPS-compatible image (for example, `redislabs/redis:\u003cversion\u003e.fips`). The field defaults to `false`.\n\n## Pull the image by digest\n\nIf you pin the image by digest (`spec.redisEnterpriseImageSpec`) instead of by tag, the operator can't add the `.fips` suffix. In that case, supply a digest that points to a FIPS-compatible image yourself.\n",
  "tags": ["docs","operate","kubernetes"],
  "last_updated": "2026-10-19T14:33:15-05:00"
}