Radius.Data/redisCaches@2025-08-01-preview

Description

The Radius.Data/redisCaches Resource Type deploys a Redis cache. To deploy a Redis cache, add a redisCaches resource to the application definition Bicep file. Unlike database types, no credential has to be supplied: the cache generates its own access key, so the platform-engineer recipe needs no injected credentials.

resource cache 'Radius.Data/redisCaches@2025-08-01-preview' = {
  name: 'redis'
  properties: {
    environment: environment
    application: myApplication.id
    size: 'S'
  }
}

To connect your container to the cache, create a connection from the Container resource to the cache as shown below.

resource frontend 'Radius.Compute/containers@2025-08-01-preview' = {
  name: 'frontend'
  properties: {
    application: myApplication.id
    environment: environment
    containers: {
      frontend: {
        image: 'frontend:1.25'
      }
    }
    connections: {
      redis: {
        source: cache.id
      }
    }
  }
}

On compatible Kubernetes Container Recipes, the connection injects environment variables into the container for the cache properties. The variables are named CONNECTION_<CONNECTION-NAME>_<PROPERTY-NAME>. In this example the connection name is redis so the environment variables will be:

• CONNECTION_REDIS_HOST
• CONNECTION_REDIS_PORT

Recipe-generated secrets are materialized into a managed Radius.Security/secrets resource. With Radius control-plane support from radius-project/radius#12709 and Kubernetes Container Recipe support from resource-types-contrib#300 or later, the same redis connection injects each key returned in result.secrets: CONNECTION_REDIS_URL, and CONNECTION_REDIS_ACCESSKEY when the Recipe returns accessKey. host and port remain ordinary values.

For custom, older, or mixed-version Kubernetes deployments, bind the key explicitly with secretKeyRef, using cache.properties.secrets.name as the secretName. Use url for a client that parses a connection URL, or accessKey for a client that takes host, port, and password separately:

env: {
  REDIS_ADDR: {
    value: '${cache.properties.host}:${cache.properties.port}'
  }
  REDIS_PASSWORD: {
    valueFrom: {
      secretKeyRef: {
        secretName: cache.properties.secrets.name
        key: 'accessKey'
      }
    }
  }
}

A recipe that provisions a cache requiring no credential does not map accessKey; bind it only against a recipe that declares it.

Top-Level Properties

Object Properties

connections

secrets