From 9866e796de70e4a8af75aa36d4b49e179266020e Mon Sep 17 00:00:00 2001 From: Robert Shelton Date: Fri, 13 Nov 2026 16:37:39 -0500 Subject: [PATCH 1/2] Iris docs: arm64 support in redis-iris 1.0.1 redis-iris 1.0.1 publishes every image for linux/amd64 and linux/arm64. Tested on Apple silicon with a native arm64 kind node, no emulation: helm test passes for all five products. - Architecture: amd64 or arm64; drop the Apple silicon emulation section. - Rollback to 1.0.0 isn't possible on arm64 nodes. - Memory queue monitor: asynqmon -> asynqdash, Ingress delete step, optional REDIS_USERNAME. - Mirror with skopeo copy --all. - Pin installs and image tags to 1.0.1; fix the Memory NetworkPolicy path. Co-Authored-By: Claude Opus 5.5 --- .../iris/agent-memory/self-managed/_index.md | 2 +- .../iris/agent-memory/self-managed/deploy.md | 2 +- .../agent-memory/self-managed/operations.md | 7 +++--- .../self-managed/prerequisites.md | 22 +++++++++---------- .../agent-memory/self-managed/reference.md | 4 ++-- .../agent-playbook/self-managed/_index.md | 2 +- .../self-managed/configuration.md | 6 ++--- .../agent-playbook/self-managed/deploy.md | 2 +- .../agent-playbook/self-managed/extraction.md | 2 +- .../self-managed/prerequisites.md | 6 ++--- .../context-gateway/self-managed/_index.md | 2 +- .../context-gateway/self-managed/deploy.md | 2 +- .../self-managed/prerequisites.md | 2 +- .../context-gateway/self-managed/reference.md | 4 ++-- .../identity-service/self-managed/_index.md | 2 +- .../identity-service/self-managed/deploy.md | 4 ++-- .../self-managed/prerequisites.md | 2 +- .../iris/intent-router/self-managed/_index.md | 2 +- .../iris/intent-router/self-managed/deploy.md | 2 +- .../self-managed/prerequisites.md | 2 +- .../operate/iris/lens/self-managed/_index.md | 2 +- .../operate/iris/lens/self-managed/deploy.md | 2 +- .../iris/lens/self-managed/prerequisites.md | 2 +- content/operate/iris/self-managed/_index.md | 19 ++++------------ .../operate/iris/self-managed/operations.md | 12 +++++++--- 25 files changed, 54 insertions(+), 62 deletions(-) diff --git a/content/operate/iris/agent-memory/self-managed/_index.md b/content/operate/iris/agent-memory/self-managed/_index.md index 4df053ccf0..5c51f0e73a 100644 --- a/content/operate/iris/agent-memory/self-managed/_index.md +++ b/content/operate/iris/agent-memory/self-managed/_index.md @@ -29,7 +29,7 @@ documents the self-managed admin endpoints for stores. ## What you are deploying -The `redis-iris` chart `1.0.0` deploys the Agent Memory Data Plane, workers, and Control Plane, +The `redis-iris` chart `1.0.1` deploys the Agent Memory Data Plane, workers, and Control Plane, with the Identity Service and the Iris console, under fixed names. Agent Memory's values go under the `memory:` key, and the chart's `examples/memory-only.yaml` is a working values file to start from. You provide the Redis databases. diff --git a/content/operate/iris/agent-memory/self-managed/deploy.md b/content/operate/iris/agent-memory/self-managed/deploy.md index 9faff82a30..5d34a84c1a 100644 --- a/content/operate/iris/agent-memory/self-managed/deploy.md +++ b/content/operate/iris/agent-memory/self-managed/deploy.md @@ -205,7 +205,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.0 \ + --version 1.0.1 \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/agent-memory/self-managed/operations.md b/content/operate/iris/agent-memory/self-managed/operations.md index e5f444463c..061b8479d2 100644 --- a/content/operate/iris/agent-memory/self-managed/operations.md +++ b/content/operate/iris/agent-memory/self-managed/operations.md @@ -113,7 +113,7 @@ and then removes what it created. See [Verify the deployment](/content/operate/i ## FIPS -The suite chart `1.0.0` doesn't support the Federal Information Processing Standards (FIPS) +The suite chart `1.0.1` doesn't support the Federal Information Processing Standards (FIPS) profile. `global.security.profile: fips` fails the install. See [Not supported in this release](/content/operate/iris/self-managed/_index.md#not-supported-in-this-release). @@ -125,11 +125,10 @@ the direct caller also has a valid Redis Agent Memory credential. The Agent Memory chart inside the suite package includes `networkpolicy.reference.yaml` as a reference manifest. It is not templated, because allowed callers are environment-specific. Get it -from the suite package: +from the suite package, at `redis-iris/charts/redis-agent-memory/networkpolicy.reference.yaml`: ```bash -helm pull redis-ai/redis-iris --version 1.0.0 --untar -tar -xzf redis-iris/charts/redis-agent-memory-1.0.0.tgz redis-agent-memory/networkpolicy.reference.yaml +helm pull redis-ai/redis-iris --version 1.0.1 --untar ``` Customize the placeholders before applying it: diff --git a/content/operate/iris/agent-memory/self-managed/prerequisites.md b/content/operate/iris/agent-memory/self-managed/prerequisites.md index 1dcaf08a13..0c0da0b629 100644 --- a/content/operate/iris/agent-memory/self-managed/prerequisites.md +++ b/content/operate/iris/agent-memory/self-managed/prerequisites.md @@ -15,7 +15,7 @@ aliases: - /operate/iris/agent-memory/self-managed/plan-deployment/ --- -Agent Memory installs as the `memory` service of the `redis-iris` Helm chart `1.0.0`, from the +Agent Memory installs as the `memory` service of the `redis-iris` Helm chart `1.0.1`, from the Redis AI Helm repository `https://helm.redis.io/ai`. The suite deploys the Agent Memory Data Plane, workers, and Control Plane, with the Identity Service and the Iris console. Start with the [suite prerequisites](/content/operate/iris/self-managed/_index.md#prerequisites). This page adds @@ -25,8 +25,8 @@ what Agent Memory needs. | Item | Where it comes from | | ---- | ------------------- | -| Helm chart | `redis-ai/redis-iris` `1.0.0` | -| Container images | Docker Hub: `redislabs/agent-memory:1.0.0` and `redislabs/agent-memory-control-plane:1.0.0`, plus the Identity Service and console images the suite installs | +| Helm chart | `redis-ai/redis-iris` `1.0.1` | +| Container images | Docker Hub: `redislabs/agent-memory:1.0.1` and `redislabs/agent-memory-control-plane:1.0.1`, plus the Identity Service and console images the suite installs | | Redis databases | You provide Store Redis, Job Redis, and Metadata Redis | | License key | One suite license. Contact your Redis representative or [contact sales](https://redis.io/contact/). | | Provider credentials | You provide embedding provider credentials and, when worker features are enabled, promotion or summarization LLM credentials | @@ -109,21 +109,19 @@ other components the suite installs: | Image | Needed | | --- | --- | -| `redislabs/agent-memory:1.0.0` | Always (Data Plane and workers) | -| `redislabs/agent-memory-control-plane:1.0.0` | Always | -| `redislabs/iris-identity-service:1.0.0` | Always | +| `redislabs/agent-memory:1.0.1` | Always (Data Plane and workers) | +| `redislabs/agent-memory-control-plane:1.0.1` | Always | +| `redislabs/iris-identity-service:1.0.1` | Always | | `curlimages/curl:8.17.0` | The suite preflight (`preflight.image`) | | `python:3.13-alpine` | `helm test iris` (`tests.suiteVerify.image`) | -| `hibiken/asynqmon:0.7.2` | Optional, with `memory.controlplane.queueMonitor` | +| `ghcr.io/jpedrosouza/asynqdash:1.2.0` | Optional, with `memory.controlplane.queueMonitor` | ```bash -docker pull redislabs/agent-memory:1.0.0 -docker tag redislabs/agent-memory:1.0.0 \ - registry.example.com/redislabs/agent-memory:1.0.0 -docker push registry.example.com/redislabs/agent-memory:1.0.0 +skopeo copy --all docker://redislabs/agent-memory:1.0.1 \ + docker://registry.example.com/redislabs/agent-memory:1.0.1 ``` -Repeat for each image. If the registry requires authentication, create an image pull Secret: +Repeat for each image. `--all` copies every platform. `docker pull` and `docker push` copy only your workstation's, so nodes of the other platform can't pull the image. If the registry requires authentication, create an image pull Secret: ```bash kubectl -n create secret docker-registry iris-registry \ diff --git a/content/operate/iris/agent-memory/self-managed/reference.md b/content/operate/iris/agent-memory/self-managed/reference.md index 57a25c6ab7..365d9d072e 100644 --- a/content/operate/iris/agent-memory/self-managed/reference.md +++ b/content/operate/iris/agent-memory/self-managed/reference.md @@ -77,8 +77,8 @@ CSI-synced Secrets, make sure a Control Plane pod also mounts the corresponding | Need | Reference | | --- | --- | -| Suite chart values | `helm show values redis-ai/redis-iris --version 1.0.0` | -| Agent Memory chart values and README | `charts/redis-agent-memory-1.0.0.tgz` in the suite package (`helm pull redis-ai/redis-iris --version 1.0.0 --untar`) | +| Suite chart values | `helm show values redis-ai/redis-iris --version 1.0.1` | +| Agent Memory chart values and README | `redis-iris/charts/redis-agent-memory/` in the suite package (`helm pull redis-ai/redis-iris --version 1.0.1 --untar`) | | NetworkPolicy reference | [Network policy](/content/operate/iris/agent-memory/self-managed/operations.md#network-policy) | | Redis Agent Memory API reference | [Redis Agent Memory API]({{< relref "/develop/ai/context-engine/agent-memory/api-reference" >}}) | | Control Plane API reference | [Control Plane API reference]({{< relref "/operate/iris/agent-memory/self-managed/control-plane-api-reference" >}}) | diff --git a/content/operate/iris/agent-playbook/self-managed/_index.md b/content/operate/iris/agent-playbook/self-managed/_index.md index c0231d56ec..4389c84e02 100644 --- a/content/operate/iris/agent-playbook/self-managed/_index.md +++ b/content/operate/iris/agent-playbook/self-managed/_index.md @@ -17,7 +17,7 @@ Redis Agent Playbooks store the answers and procedures your business approves as This guide is for that administrator. It covers deploying Agent Playbooks on your own Kubernetes cluster, then configuring, securing, and operating it. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/agent-playbook/self-managed/deploy.md). -The `redis-iris` chart `1.0.0` deploys the Agent Playbooks control plane and data plane, and optionally a background extraction worker, with the Identity Service that issues and checks agent keys. Agent Playbooks values go under the `playbook:` key, and the chart's `examples/playbook.yaml` is a working values file to start from. You provide the Redis databases, the embedding provider, and the suite license. The chart doesn't install Redis. +The `redis-iris` chart `1.0.1` deploys the Agent Playbooks control plane and data plane, and optionally a background extraction worker, with the Identity Service that issues and checks agent keys. Agent Playbooks values go under the `playbook:` key, and the chart's `examples/playbook.yaml` is a working values file to start from. You provide the Redis databases, the embedding provider, and the suite license. The chart doesn't install Redis. Applications call the data plane to author, review, and retrieve entries, as described in the [data-plane API reference](/content/develop/ai/context-engine/agent-playbooks/api-reference.md). The [control-plane API reference](/content/operate/iris/agent-playbook/self-managed/control-plane-api-reference.md) documents the administration endpoints for playbooks. diff --git a/content/operate/iris/agent-playbook/self-managed/configuration.md b/content/operate/iris/agent-playbook/self-managed/configuration.md index d565c7b2ca..0a20e53d53 100644 --- a/content/operate/iris/agent-playbook/self-managed/configuration.md +++ b/content/operate/iris/agent-playbook/self-managed/configuration.md @@ -11,7 +11,7 @@ weight: 30 hideListLinks: true --- -The `redis-iris` chart `1.0.0` renders the Agent Playbooks control-plane and data-plane configuration from the `playbook:` values in `iris-values.yaml`. Storage URLs and provider credentials stay in Secrets you create. The suite supplies the tenant, the license, and the Identity Service connection and credentials, as [Add the Agent Playbooks values](/content/operate/iris/agent-playbook/self-managed/deploy.md#2-add-the-agent-playbooks-values) lists. +The `redis-iris` chart `1.0.1` renders the Agent Playbooks control-plane and data-plane configuration from the `playbook:` values in `iris-values.yaml`. Storage URLs and provider credentials stay in Secrets you create. The suite supplies the tenant, the license, and the Identity Service connection and credentials, as [Add the Agent Playbooks values](/content/operate/iris/agent-playbook/self-managed/deploy.md#2-add-the-agent-playbooks-values) lists. ## Storage configuration @@ -86,7 +86,7 @@ The install fails with a named message when a required value is missing: `playbo For every value and its default, see the [configuration reference](/content/operate/iris/agent-playbook/self-managed/reference.md#configuration-reference), or run: ```bash -helm show values redis-ai/redis-iris --version 1.0.0 +helm show values redis-ai/redis-iris --version 1.0.1 ``` ## Trust a private CA @@ -102,7 +102,7 @@ Set `global.tls.caCertSecret: playbook-ca` for every service, or `playbook.tls.c ## Configure tracing -The Federal Information Processing Standards (FIPS) profile isn't supported in `redis-iris` `1.0.0`. See [Not supported in this release](/content/operate/iris/self-managed/_index.md#not-supported-in-this-release). +The Federal Information Processing Standards (FIPS) profile isn't supported in `redis-iris` `1.0.1`. See [Not supported in this release](/content/operate/iris/self-managed/_index.md#not-supported-in-this-release). To export traces from the control plane, data plane, and extraction worker, configure a trusted OpenTelemetry Protocol (OTLP) collector: diff --git a/content/operate/iris/agent-playbook/self-managed/deploy.md b/content/operate/iris/agent-playbook/self-managed/deploy.md index beef5581e4..08c47a0bef 100644 --- a/content/operate/iris/agent-playbook/self-managed/deploy.md +++ b/content/operate/iris/agent-playbook/self-managed/deploy.md @@ -68,7 +68,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.0 \ + --version 1.0.1 \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/agent-playbook/self-managed/extraction.md b/content/operate/iris/agent-playbook/self-managed/extraction.md index 9409da1e7f..1e8dddf268 100644 --- a/content/operate/iris/agent-playbook/self-managed/extraction.md +++ b/content/operate/iris/agent-playbook/self-managed/extraction.md @@ -107,7 +107,7 @@ Upgrade the release: ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.0 \ + --version 1.0.1 \ --namespace \ -f iris-values.yaml kubectl -n rollout status deployment/redis-agent-playbook-worker diff --git a/content/operate/iris/agent-playbook/self-managed/prerequisites.md b/content/operate/iris/agent-playbook/self-managed/prerequisites.md index cef77fe90b..5237a707a0 100644 --- a/content/operate/iris/agent-playbook/self-managed/prerequisites.md +++ b/content/operate/iris/agent-playbook/self-managed/prerequisites.md @@ -11,7 +11,7 @@ weight: 20 hideListLinks: true --- -The `redis-iris` chart `1.0.0` deploys the Agent Playbooks control plane, data plane, and optional extraction worker, with the Identity Service. Start with the suite's [prerequisites](/content/operate/iris/self-managed/_index.md#prerequisites). This page lists what Agent Playbooks adds: the Redis databases, the embedding provider, and Kubernetes exposure. +The `redis-iris` chart `1.0.1` deploys the Agent Playbooks control plane, data plane, and optional extraction worker, with the Identity Service. Start with the suite's [prerequisites](/content/operate/iris/self-managed/_index.md#prerequisites). This page lists what Agent Playbooks adds: the Redis databases, the embedding provider, and Kubernetes exposure. ## What you need @@ -79,8 +79,8 @@ The suite chart pins these images: | Component | Image | | --- | --- | -| Control plane | `redislabs/iris-agent-playbook-control:1.0.0` | -| Data plane and extraction worker | `redislabs/iris-agent-playbook-data:1.0.0` | +| Control plane | `redislabs/iris-agent-playbook-control:1.0.1` | +| Data plane and extraction worker | `redislabs/iris-agent-playbook-data:1.0.1` | Allow chart downloads, image pulls, Redis connections, and data-plane access to the embedding provider. The data plane and control plane must reach the Identity Service, and the Identity Service must reach the control plane on port `9200`. For a disconnected installation, mirror the images, use a downloaded chart package, and set the image repositories and `imagePullSecrets` under `playbook:` in `iris-values.yaml`. diff --git a/content/operate/iris/context-gateway/self-managed/_index.md b/content/operate/iris/context-gateway/self-managed/_index.md index b35db17eee..e2afda12c5 100644 --- a/content/operate/iris/context-gateway/self-managed/_index.md +++ b/content/operate/iris/context-gateway/self-managed/_index.md @@ -13,7 +13,7 @@ aliases: - /operate/iris/context-retriever/self-managed/ --- -The `redis-iris` chart `1.0.0` deploys the Context Gateway Control Plane and Data Plane, with the Identity Service that issues and checks agent keys. Context Gateway values go under the `contextGateway:` key, and the chart's `examples/context-gateway.yaml` is a working values file to start from. You provide the Redis databases, the `https://` origin MCP clients reach the Data Plane at, and the suite license. The chart doesn't install Redis, Vault, or Secrets Store CSI (Container Storage Interface) Driver resources. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/context-gateway/self-managed/deploy.md). +The `redis-iris` chart `1.0.1` deploys the Context Gateway Control Plane and Data Plane, with the Identity Service that issues and checks agent keys. Context Gateway values go under the `contextGateway:` key, and the chart's `examples/context-gateway.yaml` is a working values file to start from. You provide the Redis databases, the `https://` origin MCP clients reach the Data Plane at, and the suite license. The chart doesn't install Redis, Vault, or Secrets Store CSI (Container Storage Interface) Driver resources. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/context-gateway/self-managed/deploy.md). Agents call the Data Plane's Model Context Protocol (MCP) endpoint, described in the [MCP API Reference](/content/develop/ai/context-engine/context-gateway/api-reference.md). The [Control Plane API Reference](/content/operate/iris/context-gateway/self-managed/control-plane-api-reference.md) documents the self-managed administration endpoints for Gateways and Upstreams. diff --git a/content/operate/iris/context-gateway/self-managed/deploy.md b/content/operate/iris/context-gateway/self-managed/deploy.md index bc0f220a5f..64b76348f9 100644 --- a/content/operate/iris/context-gateway/self-managed/deploy.md +++ b/content/operate/iris/context-gateway/self-managed/deploy.md @@ -89,7 +89,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.0 \ + --version 1.0.1 \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/context-gateway/self-managed/prerequisites.md b/content/operate/iris/context-gateway/self-managed/prerequisites.md index 7e55850710..7f700894ed 100644 --- a/content/operate/iris/context-gateway/self-managed/prerequisites.md +++ b/content/operate/iris/context-gateway/self-managed/prerequisites.md @@ -110,7 +110,7 @@ Redis URLs, tokens, keyrings, and the license belong in Kubernetes Secrets or Se The chart defaults to these repositories and pins the image tags that match its chart version. Leave `image.repository` and `image.tag` unset for a public install, and override them only to pull from a mirror. -Chart `1.0.0` pins both images to tag `1.0.0`. +Chart `1.0.1` pins both images to tag `1.0.1`. ## Air-gapped and private registry installs diff --git a/content/operate/iris/context-gateway/self-managed/reference.md b/content/operate/iris/context-gateway/self-managed/reference.md index 580fe13766..6fb1983ce2 100644 --- a/content/operate/iris/context-gateway/self-managed/reference.md +++ b/content/operate/iris/context-gateway/self-managed/reference.md @@ -58,6 +58,6 @@ Each file reference accepts a Kubernetes Secret or a Secrets Store Container Sto | Need | Reference | | --- | --- | -| Helm chart values | `helm show values redis-ai/redis-iris --version 1.0.0`, with Context Gateway under `contextGateway:` | +| Helm chart values | `helm show values redis-ai/redis-iris --version 1.0.1`, with Context Gateway under `contextGateway:` | | Chart examples | `examples/context-gateway.yaml` in the `redis-iris` chart package | -| Chart README | `helm show readme redis-ai/redis-iris --version 1.0.0` | +| Chart README | `helm show readme redis-ai/redis-iris --version 1.0.1` | diff --git a/content/operate/iris/identity-service/self-managed/_index.md b/content/operate/iris/identity-service/self-managed/_index.md index 1b152ed2f1..2b28fd7382 100644 --- a/content/operate/iris/identity-service/self-managed/_index.md +++ b/content/operate/iris/identity-service/self-managed/_index.md @@ -17,7 +17,7 @@ The Identity Service is the one place where a self-managed Redis Iris installati 1. It keeps the grants of each key. A grant says which resource the caller can use, and how. 1. It answers the data planes when they ask whether a key is valid, and what it can do. -This guide is for the platform administrator who installs the Identity Service, manages agent keys, and manages operator access. The `redis-iris` chart `1.0.0` always installs the Identity Service, as `iris-identity-service`. Its values go under the `identityService:` key, with the shared values under `global.iris`. It needs no license of its own, because the suite license covers it. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/identity-service/self-managed/deploy.md). +This guide is for the platform administrator who installs the Identity Service, manages agent keys, and manages operator access. The `redis-iris` chart `1.0.1` always installs the Identity Service, as `iris-identity-service`. Its values go under the `identityService:` key, with the shared values under `global.iris`. It needs no license of its own, because the suite license covers it. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/identity-service/self-managed/deploy.md). ## What you deploy diff --git a/content/operate/iris/identity-service/self-managed/deploy.md b/content/operate/iris/identity-service/self-managed/deploy.md index a2f63e5867..c21c2bfa09 100644 --- a/content/operate/iris/identity-service/self-managed/deploy.md +++ b/content/operate/iris/identity-service/self-managed/deploy.md @@ -73,9 +73,9 @@ Run the [suite preflight](/content/operate/iris/self-managed/_index.md#4-run-the ```bash helm repo add redis-ai https://helm.redis.io/ai helm repo update redis-ai -helm pull redis-ai/redis-iris --version 1.0.0 --untar +helm pull redis-ai/redis-iris --version 1.0.1 --untar helm install iris redis-ai/redis-iris \ - --version 1.0.0 \ + --version 1.0.1 \ --namespace \ -f redis-iris/examples/memory-only.yaml \ -f iris-values.yaml diff --git a/content/operate/iris/identity-service/self-managed/prerequisites.md b/content/operate/iris/identity-service/self-managed/prerequisites.md index 22f78e3860..f0b61f34d3 100644 --- a/content/operate/iris/identity-service/self-managed/prerequisites.md +++ b/content/operate/iris/identity-service/self-managed/prerequisites.md @@ -17,7 +17,7 @@ The Identity Service depends on a metadata Redis and Secrets that you set up fir | Requirement | Detail | | --- | --- | -| Suite chart | `redis-iris` chart `1.0.0` in the Redis AI Helm repository, `https://helm.redis.io/ai`. The suite prerequisites list the Kubernetes, Helm, and Metrics API versions. | +| Suite chart | `redis-iris` chart `1.0.1` in the Redis AI Helm repository, `https://helm.redis.io/ai`. The suite prerequisites list the Kubernetes, Helm, and Metrics API versions. | | Namespace | A namespace that holds only this release. The examples use ``. | | Metadata Redis | A Redis database for the Identity Service, as described in [Metadata Redis](#metadata-redis). | | `kubectl`, `curl` | For the install and administration examples. | diff --git a/content/operate/iris/intent-router/self-managed/_index.md b/content/operate/iris/intent-router/self-managed/_index.md index 87d8629ccc..6ab53482e7 100644 --- a/content/operate/iris/intent-router/self-managed/_index.md +++ b/content/operate/iris/intent-router/self-managed/_index.md @@ -15,7 +15,7 @@ Intent Router classifies each incoming user message by intent, so your applicati This guide is for that administrator. It covers deploying Intent Router on your own Kubernetes cluster, then configuring, securing, and operating it. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/intent-router/self-managed/deploy.md). -The `redis-iris` chart `1.0.0` deploys the Intent Router control plane and data plane, with the Identity Service that issues and checks agent keys. Intent Router values go under the `intent:` key, and the chart's `examples/intent.yaml` is a working values file to start from. You provide the Redis databases, the embedding provider credentials, and the suite license. +The `redis-iris` chart `1.0.1` deploys the Intent Router control plane and data plane, with the Identity Service that issues and checks agent keys. Intent Router values go under the `intent:` key, and the chart's `examples/intent.yaml` is a working values file to start from. You provide the Redis databases, the embedding provider credentials, and the suite license. Applications call the data plane to author intents and match queries, as described in the [data-plane API reference](/content/develop/ai/context-engine/intent-router/api-reference.md). The [control-plane API reference](/content/operate/iris/intent-router/self-managed/control-plane-api-reference.md) documents the administration endpoints for Routers. diff --git a/content/operate/iris/intent-router/self-managed/deploy.md b/content/operate/iris/intent-router/self-managed/deploy.md index 4b3627d52e..ee1f7fec00 100644 --- a/content/operate/iris/intent-router/self-managed/deploy.md +++ b/content/operate/iris/intent-router/self-managed/deploy.md @@ -70,7 +70,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.0 \ + --version 1.0.1 \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/intent-router/self-managed/prerequisites.md b/content/operate/iris/intent-router/self-managed/prerequisites.md index 0e336e0a57..5788e78653 100644 --- a/content/operate/iris/intent-router/self-managed/prerequisites.md +++ b/content/operate/iris/intent-router/self-managed/prerequisites.md @@ -78,7 +78,7 @@ Create these Secrets before you install: the storage Secret that holds the Redis ## Release artifacts and image tags -The chart uses two images, `redislabs/iris-intent-router-control` and `redislabs/iris-intent-router-data`, tagged with the chart version, such as `1.0.0`. Rendering fails with a named message when a `tag` is empty. To install from a private registry, mirror both images, then set `controlplane.image.repository`, `dataplane.image.repository`, and `imagePullSecrets`. +The chart uses two images, `redislabs/iris-intent-router-control` and `redislabs/iris-intent-router-data`, tagged with the chart version, such as `1.0.1`. Rendering fails with a named message when a `tag` is empty. To install from a private registry, mirror both images, then set `controlplane.image.repository`, `dataplane.image.repository`, and `imagePullSecrets`. ## Helm values to review diff --git a/content/operate/iris/lens/self-managed/_index.md b/content/operate/iris/lens/self-managed/_index.md index e38cdc6e36..f5a3cc1659 100644 --- a/content/operate/iris/lens/self-managed/_index.md +++ b/content/operate/iris/lens/self-managed/_index.md @@ -17,7 +17,7 @@ This guide is for that administrator. It covers deploying Lens on your own Kuber ## What you deploy -The `redis-iris` chart `1.0.0` runs three Lens workloads, with the Identity Service. Lens values go under the `lens:` key, and the chart's `examples/lens.yaml` is a working values file to start from. +The `redis-iris` chart `1.0.1` runs three Lens workloads, with the Identity Service. Lens values go under the `lens:` key, and the chart's `examples/lens.yaml` is a working values file to start from. | Component | Purpose | Service port | | --- | --- | --- | diff --git a/content/operate/iris/lens/self-managed/deploy.md b/content/operate/iris/lens/self-managed/deploy.md index 3161aeea05..79a75e11da 100644 --- a/content/operate/iris/lens/self-managed/deploy.md +++ b/content/operate/iris/lens/self-managed/deploy.md @@ -52,7 +52,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.0 \ + --version 1.0.1 \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/lens/self-managed/prerequisites.md b/content/operate/iris/lens/self-managed/prerequisites.md index 270a771254..df11b0a301 100644 --- a/content/operate/iris/lens/self-managed/prerequisites.md +++ b/content/operate/iris/lens/self-managed/prerequisites.md @@ -23,7 +23,7 @@ Self-managed Lens runs on your Kubernetes cluster as part of the `redis-iris` su | Identity Service | Installed by the suite, as `iris-identity-service`. | | Redis databases | A records database, a content database, and a metadata Redis, as described in [Redis databases](#redis-databases). | | Container images | Docker Hub: `redislabs/iris-lens-data` (data plane and worker) and `redislabs/iris-lens-control` (control plane). | -| Helm chart | `redis-iris` chart `1.0.0` in the Redis AI Helm repository, `https://helm.redis.io/ai`. | +| Helm chart | `redis-iris` chart `1.0.1` in the Redis AI Helm repository, `https://helm.redis.io/ai`. | | License key | The suite license. Contact your Redis representative or [contact sales](https://redis.io/contact/). | ## Redis databases diff --git a/content/operate/iris/self-managed/_index.md b/content/operate/iris/self-managed/_index.md index 7a6ab0847b..715e13f081 100644 --- a/content/operate/iris/self-managed/_index.md +++ b/content/operate/iris/self-managed/_index.md @@ -40,7 +40,7 @@ Install one release per namespace, and keep other Iris releases out of that name | Requirement | Details | | --- | --- | | Kubernetes | Kubernetes 1.28 or later. The baseline is 3 worker nodes with 12 vCPU and 24 GiB allocatable in total. The [preflight](#4-run-the-preflight) warns below it. | -| Node architecture | `linux/amd64`. The `1.0.0` images are published for `amd64` only. To evaluate on Apple silicon, see [Evaluate on a local kind cluster](#evaluate-on-a-local-kind-cluster). | +| Node architecture | `linux/amd64` or `linux/arm64`. Each `1.0.1` image tag is one multi-platform image, so every node pulls its own. The `1.0.0` images are `amd64` only. | | Metrics API | `metrics.k8s.io/v1beta1`, so the HorizontalPodAutoscalers can scale. | | Helm | Helm 3.10 or later, with the Redis AI repository `https://helm.redis.io/ai`. Helm 4 isn't supported in this release. | | `kubectl` | Configured for the cluster and namespace. | @@ -163,7 +163,7 @@ ui: Every service is installed by default. Turn one off with `global.iris.products..enabled: false`, where `` is `memory`, `playbook`, `lens`, `contextGateway`, or `intent`. The chart's `examples/` folder has one values file per service, which you can pass as extra `-f` files: ```bash -helm pull redis-ai/redis-iris --version 1.0.0 --untar +helm pull redis-ai/redis-iris --version 1.0.1 --untar ls redis-iris/examples ``` @@ -205,7 +205,7 @@ The chart includes a preflight that checks the cluster before an install. It rea Run it with the [`kubectl preflight`](https://troubleshoot.sh/docs/#installation) plugin, v0.124.0 or later. Older versions only warn on the ingress class check. The namespace must exist: ```bash -helm template iris redis-ai/redis-iris --version 1.0.0 -n -f iris-values.yaml \ +helm template iris redis-ai/redis-iris --version 1.0.1 -n -f iris-values.yaml \ --show-only templates/preflight.yaml \ | yq '.stringData["preflight.yaml"]' | kubectl preflight - ``` @@ -231,7 +231,7 @@ kubectl create clusterrolebinding -issuer-discovery \ helm repo add redis-ai https://helm.redis.io/ai helm repo update redis-ai helm install iris redis-ai/redis-iris \ - --version 1.0.0 \ + --version 1.0.1 \ --namespace \ -f iris-values.yaml ``` @@ -377,17 +377,6 @@ You can evaluate the suite on a [kind](https://kind.sigs.k8s.io/) cluster on you You need Docker Desktop, `kind`, `kubectl`, Helm 3.10 or later, and your license file. -### Run the `amd64` images on Apple silicon - -The `1.0.0` images are published for `amd64` only. On Apple silicon, create a native `arm64` kind node, which is the default. Docker Desktop's x86 emulation then runs the `amd64` images inside it. - -Don't create an `amd64` kind node. Under QEMU emulation the kubelet reports `seccomp is not supported` and the node doesn't start. If you rebuilt a cluster and Docker cached the `kindest/node` image as `amd64`, check and remove it before you create the cluster again: - -```bash -docker image inspect kindest/node: --format '{{.Architecture}}' -docker rmi kindest/node: -``` - ### Start throwaway Redis databases Five Redis deployments cover every service: diff --git a/content/operate/iris/self-managed/operations.md b/content/operate/iris/self-managed/operations.md index 0a54a66af6..a4945b98e4 100644 --- a/content/operate/iris/self-managed/operations.md +++ b/content/operate/iris/self-managed/operations.md @@ -39,6 +39,12 @@ Helm upgrades every component at the same time. Upgrade within one minor version With `--atomic`, Helm returns to the previous revision by itself when the upgrade doesn't become ready. It reverts Kubernetes resources and Helm values, but it doesn't undo writes to Redis. A value that the new version refuses fails the render, names the field, and applies nothing. +`1.0.1` renames the Agent Memory queue monitor from `redis-agent-memory-asynqmon` to `redis-agent-memory-asynqdash`. If you turned on its Ingress, delete the old one before you upgrade to `1.0.1` or roll back to `1.0.0`, and update any NetworkPolicy or monitoring rule that matches the old name: + +```bash +kubectl -n delete ingress redis-agent-memory-asynqmon +``` + ### Recover an interrupted upgrade An upgrade whose client was interrupted leaves the release in `pending-upgrade`, and Helm refuses every later upgrade. Find the last `deployed` revision, then roll back to it: @@ -54,7 +60,7 @@ helm rollback iris --namespace --wait --timeout 15m helm rollback iris --namespace --wait --timeout 15m ``` -A rollback restores the workloads and the values of that revision. It doesn't undo data or metadata written to Redis. It never restores a credential: the generated Secrets aren't part of the release, so a rotated or revoked value stays rotated or revoked. The same version rules as for an upgrade apply. +A rollback restores the workloads and the values of that revision. It doesn't undo data or metadata written to Redis. It never restores a credential: the generated Secrets aren't part of the release, so a rotated or revoked value stays rotated or revoked. The same version rules as for an upgrade apply. You can't roll back to `1.0.0` on `arm64` nodes, because its images are `amd64` only. Keep the chart of each version you install, so you can roll back without the repository: @@ -72,7 +78,7 @@ These values name Secrets that can hold the metadata Redis connection. Check eve | --- | --- | --- | | Identity Service | `identityService.metadata.existingSecret` | `metadata.urls` | | Agent Memory | `memory.secrets.secretName` | The `metadata`, `databases`, and `background_jobs` URLs | -| Agent Memory queue monitor, with `memory.controlplane.queueMonitor.enabled` | `memory.controlplane.queueMonitor.redis.existingSecret` | `REDIS_URL`, the `background_jobs` Redis | +| Agent Memory queue monitor, with `memory.controlplane.queueMonitor.enabled` | `memory.controlplane.queueMonitor.redis.existingSecret` | `REDIS_URL`, the `background_jobs` Redis, and optionally `REDIS_USERNAME` | | Agent Playbooks | `playbook.storage.existingSecret` | `storage.metadata`, and `storage.content` | | Agent Playbooks worker, with extraction | `playbook.worker.existingSecret` | `worker.redis`, the extraction queue | | Lens | `lens.storage.existingSecret` | `storage.metadata` in both planes | @@ -92,7 +98,7 @@ These values name Secrets that can hold the metadata Redis connection. Check eve restart iris-identity-service restart redis-agent-memory-controlplane redis-agent-playbook-controlplane redis-lens-controlplane \ redis-context-gateway-controlplane redis-intent-router-controlplane - restart redis-agent-memory redis-agent-memory-worker redis-agent-memory-asynqmon redis-agent-playbook-dataplane \ + restart redis-agent-memory redis-agent-memory-worker redis-agent-memory-asynqdash redis-agent-playbook-dataplane \ redis-agent-playbook-worker redis-lens-dataplane redis-lens-worker redis-context-gateway-dataplane \ redis-intent-router-dataplane restart iris-ui iris-ui-auth From ceac9a4ef134e41dac4562effba1823ea4702461 Mon Sep 17 00:00:00 2001 From: Robert Shelton Date: Fri, 13 Nov 2026 16:41:09 -0500 Subject: [PATCH 2/2] Iris docs: pin the redis-iris 1.0 line, not a patch Commands use --version '~1.0.1', prose says 1.0, and image tables say each tag is the chart version, so a new 1.0 patch needs no docs edit. Rollback reads the installed version from helm list. Co-Authored-By: Claude Opus 5.5 --- .../iris/agent-memory/self-managed/_index.md | 2 +- .../iris/agent-memory/self-managed/deploy.md | 2 +- .../agent-memory/self-managed/operations.md | 4 ++-- .../agent-memory/self-managed/prerequisites.md | 18 +++++++++--------- .../agent-memory/self-managed/reference.md | 4 ++-- .../iris/agent-playbook/self-managed/_index.md | 2 +- .../self-managed/configuration.md | 6 +++--- .../iris/agent-playbook/self-managed/deploy.md | 2 +- .../agent-playbook/self-managed/extraction.md | 2 +- .../self-managed/prerequisites.md | 8 ++++---- .../context-gateway/self-managed/_index.md | 2 +- .../context-gateway/self-managed/deploy.md | 2 +- .../self-managed/prerequisites.md | 2 +- .../context-gateway/self-managed/reference.md | 4 ++-- .../identity-service/self-managed/_index.md | 2 +- .../identity-service/self-managed/deploy.md | 4 ++-- .../self-managed/prerequisites.md | 2 +- .../iris/intent-router/self-managed/_index.md | 2 +- .../iris/intent-router/self-managed/deploy.md | 2 +- .../operate/iris/lens/self-managed/_index.md | 2 +- .../operate/iris/lens/self-managed/deploy.md | 2 +- .../iris/lens/self-managed/prerequisites.md | 2 +- content/operate/iris/self-managed/_index.md | 8 ++++---- .../operate/iris/self-managed/operations.md | 2 +- 24 files changed, 44 insertions(+), 44 deletions(-) diff --git a/content/operate/iris/agent-memory/self-managed/_index.md b/content/operate/iris/agent-memory/self-managed/_index.md index 5c51f0e73a..278d8dd7f8 100644 --- a/content/operate/iris/agent-memory/self-managed/_index.md +++ b/content/operate/iris/agent-memory/self-managed/_index.md @@ -29,7 +29,7 @@ documents the self-managed admin endpoints for stores. ## What you are deploying -The `redis-iris` chart `1.0.1` deploys the Agent Memory Data Plane, workers, and Control Plane, +The `redis-iris` chart `1.0` deploys the Agent Memory Data Plane, workers, and Control Plane, with the Identity Service and the Iris console, under fixed names. Agent Memory's values go under the `memory:` key, and the chart's `examples/memory-only.yaml` is a working values file to start from. You provide the Redis databases. diff --git a/content/operate/iris/agent-memory/self-managed/deploy.md b/content/operate/iris/agent-memory/self-managed/deploy.md index 5d34a84c1a..a7a8fe1e96 100644 --- a/content/operate/iris/agent-memory/self-managed/deploy.md +++ b/content/operate/iris/agent-memory/self-managed/deploy.md @@ -205,7 +205,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.1 \ + --version '~1.0.1' \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/agent-memory/self-managed/operations.md b/content/operate/iris/agent-memory/self-managed/operations.md index 061b8479d2..3092aa592d 100644 --- a/content/operate/iris/agent-memory/self-managed/operations.md +++ b/content/operate/iris/agent-memory/self-managed/operations.md @@ -113,7 +113,7 @@ and then removes what it created. See [Verify the deployment](/content/operate/i ## FIPS -The suite chart `1.0.1` doesn't support the Federal Information Processing Standards (FIPS) +The suite chart `1.0` doesn't support the Federal Information Processing Standards (FIPS) profile. `global.security.profile: fips` fails the install. See [Not supported in this release](/content/operate/iris/self-managed/_index.md#not-supported-in-this-release). @@ -128,7 +128,7 @@ reference manifest. It is not templated, because allowed callers are environment from the suite package, at `redis-iris/charts/redis-agent-memory/networkpolicy.reference.yaml`: ```bash -helm pull redis-ai/redis-iris --version 1.0.1 --untar +helm pull redis-ai/redis-iris --version '~1.0.1' --untar ``` Customize the placeholders before applying it: diff --git a/content/operate/iris/agent-memory/self-managed/prerequisites.md b/content/operate/iris/agent-memory/self-managed/prerequisites.md index 0c0da0b629..6859d7c22a 100644 --- a/content/operate/iris/agent-memory/self-managed/prerequisites.md +++ b/content/operate/iris/agent-memory/self-managed/prerequisites.md @@ -15,7 +15,7 @@ aliases: - /operate/iris/agent-memory/self-managed/plan-deployment/ --- -Agent Memory installs as the `memory` service of the `redis-iris` Helm chart `1.0.1`, from the +Agent Memory installs as the `memory` service of the `redis-iris` Helm chart `1.0`, from the Redis AI Helm repository `https://helm.redis.io/ai`. The suite deploys the Agent Memory Data Plane, workers, and Control Plane, with the Identity Service and the Iris console. Start with the [suite prerequisites](/content/operate/iris/self-managed/_index.md#prerequisites). This page adds @@ -25,8 +25,8 @@ what Agent Memory needs. | Item | Where it comes from | | ---- | ------------------- | -| Helm chart | `redis-ai/redis-iris` `1.0.1` | -| Container images | Docker Hub: `redislabs/agent-memory:1.0.1` and `redislabs/agent-memory-control-plane:1.0.1`, plus the Identity Service and console images the suite installs | +| Helm chart | `redis-ai/redis-iris` `1.0` | +| Container images | Docker Hub: `redislabs/agent-memory` and `redislabs/agent-memory-control-plane`, tagged with the chart version, plus the Identity Service and console images the suite installs | | Redis databases | You provide Store Redis, Job Redis, and Metadata Redis | | License key | One suite license. Contact your Redis representative or [contact sales](https://redis.io/contact/). | | Provider credentials | You provide embedding provider credentials and, when worker features are enabled, promotion or summarization LLM credentials | @@ -105,20 +105,20 @@ The suite generates Memory's runtime credential, Control Plane internal token, a ## Air-gapped and private registry installs Mirror these Agent Memory images into your internal registry, along with the images of the -other components the suite installs: +other components the suite installs. Each Redis image tag is the chart version: | Image | Needed | | --- | --- | -| `redislabs/agent-memory:1.0.1` | Always (Data Plane and workers) | -| `redislabs/agent-memory-control-plane:1.0.1` | Always | -| `redislabs/iris-identity-service:1.0.1` | Always | +| `redislabs/agent-memory` | Always (Data Plane and workers) | +| `redislabs/agent-memory-control-plane` | Always | +| `redislabs/iris-identity-service` | Always | | `curlimages/curl:8.17.0` | The suite preflight (`preflight.image`) | | `python:3.13-alpine` | `helm test iris` (`tests.suiteVerify.image`) | | `ghcr.io/jpedrosouza/asynqdash:1.2.0` | Optional, with `memory.controlplane.queueMonitor` | ```bash -skopeo copy --all docker://redislabs/agent-memory:1.0.1 \ - docker://registry.example.com/redislabs/agent-memory:1.0.1 +skopeo copy --all docker://redislabs/agent-memory: \ + docker://registry.example.com/redislabs/agent-memory: ``` Repeat for each image. `--all` copies every platform. `docker pull` and `docker push` copy only your workstation's, so nodes of the other platform can't pull the image. If the registry requires authentication, create an image pull Secret: diff --git a/content/operate/iris/agent-memory/self-managed/reference.md b/content/operate/iris/agent-memory/self-managed/reference.md index 365d9d072e..da284e7774 100644 --- a/content/operate/iris/agent-memory/self-managed/reference.md +++ b/content/operate/iris/agent-memory/self-managed/reference.md @@ -77,8 +77,8 @@ CSI-synced Secrets, make sure a Control Plane pod also mounts the corresponding | Need | Reference | | --- | --- | -| Suite chart values | `helm show values redis-ai/redis-iris --version 1.0.1` | -| Agent Memory chart values and README | `redis-iris/charts/redis-agent-memory/` in the suite package (`helm pull redis-ai/redis-iris --version 1.0.1 --untar`) | +| Suite chart values | `helm show values redis-ai/redis-iris --version '~1.0.1'` | +| Agent Memory chart values and README | `redis-iris/charts/redis-agent-memory/` in the suite package (`helm pull redis-ai/redis-iris --version '~1.0.1' --untar`) | | NetworkPolicy reference | [Network policy](/content/operate/iris/agent-memory/self-managed/operations.md#network-policy) | | Redis Agent Memory API reference | [Redis Agent Memory API]({{< relref "/develop/ai/context-engine/agent-memory/api-reference" >}}) | | Control Plane API reference | [Control Plane API reference]({{< relref "/operate/iris/agent-memory/self-managed/control-plane-api-reference" >}}) | diff --git a/content/operate/iris/agent-playbook/self-managed/_index.md b/content/operate/iris/agent-playbook/self-managed/_index.md index 4389c84e02..34c117aa88 100644 --- a/content/operate/iris/agent-playbook/self-managed/_index.md +++ b/content/operate/iris/agent-playbook/self-managed/_index.md @@ -17,7 +17,7 @@ Redis Agent Playbooks store the answers and procedures your business approves as This guide is for that administrator. It covers deploying Agent Playbooks on your own Kubernetes cluster, then configuring, securing, and operating it. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/agent-playbook/self-managed/deploy.md). -The `redis-iris` chart `1.0.1` deploys the Agent Playbooks control plane and data plane, and optionally a background extraction worker, with the Identity Service that issues and checks agent keys. Agent Playbooks values go under the `playbook:` key, and the chart's `examples/playbook.yaml` is a working values file to start from. You provide the Redis databases, the embedding provider, and the suite license. The chart doesn't install Redis. +The `redis-iris` chart `1.0` deploys the Agent Playbooks control plane and data plane, and optionally a background extraction worker, with the Identity Service that issues and checks agent keys. Agent Playbooks values go under the `playbook:` key, and the chart's `examples/playbook.yaml` is a working values file to start from. You provide the Redis databases, the embedding provider, and the suite license. The chart doesn't install Redis. Applications call the data plane to author, review, and retrieve entries, as described in the [data-plane API reference](/content/develop/ai/context-engine/agent-playbooks/api-reference.md). The [control-plane API reference](/content/operate/iris/agent-playbook/self-managed/control-plane-api-reference.md) documents the administration endpoints for playbooks. diff --git a/content/operate/iris/agent-playbook/self-managed/configuration.md b/content/operate/iris/agent-playbook/self-managed/configuration.md index 0a20e53d53..06243a1996 100644 --- a/content/operate/iris/agent-playbook/self-managed/configuration.md +++ b/content/operate/iris/agent-playbook/self-managed/configuration.md @@ -11,7 +11,7 @@ weight: 30 hideListLinks: true --- -The `redis-iris` chart `1.0.1` renders the Agent Playbooks control-plane and data-plane configuration from the `playbook:` values in `iris-values.yaml`. Storage URLs and provider credentials stay in Secrets you create. The suite supplies the tenant, the license, and the Identity Service connection and credentials, as [Add the Agent Playbooks values](/content/operate/iris/agent-playbook/self-managed/deploy.md#2-add-the-agent-playbooks-values) lists. +The `redis-iris` chart `1.0` renders the Agent Playbooks control-plane and data-plane configuration from the `playbook:` values in `iris-values.yaml`. Storage URLs and provider credentials stay in Secrets you create. The suite supplies the tenant, the license, and the Identity Service connection and credentials, as [Add the Agent Playbooks values](/content/operate/iris/agent-playbook/self-managed/deploy.md#2-add-the-agent-playbooks-values) lists. ## Storage configuration @@ -86,7 +86,7 @@ The install fails with a named message when a required value is missing: `playbo For every value and its default, see the [configuration reference](/content/operate/iris/agent-playbook/self-managed/reference.md#configuration-reference), or run: ```bash -helm show values redis-ai/redis-iris --version 1.0.1 +helm show values redis-ai/redis-iris --version '~1.0.1' ``` ## Trust a private CA @@ -102,7 +102,7 @@ Set `global.tls.caCertSecret: playbook-ca` for every service, or `playbook.tls.c ## Configure tracing -The Federal Information Processing Standards (FIPS) profile isn't supported in `redis-iris` `1.0.1`. See [Not supported in this release](/content/operate/iris/self-managed/_index.md#not-supported-in-this-release). +The Federal Information Processing Standards (FIPS) profile isn't supported in `redis-iris` `1.0`. See [Not supported in this release](/content/operate/iris/self-managed/_index.md#not-supported-in-this-release). To export traces from the control plane, data plane, and extraction worker, configure a trusted OpenTelemetry Protocol (OTLP) collector: diff --git a/content/operate/iris/agent-playbook/self-managed/deploy.md b/content/operate/iris/agent-playbook/self-managed/deploy.md index 08c47a0bef..61ad59d914 100644 --- a/content/operate/iris/agent-playbook/self-managed/deploy.md +++ b/content/operate/iris/agent-playbook/self-managed/deploy.md @@ -68,7 +68,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.1 \ + --version '~1.0.1' \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/agent-playbook/self-managed/extraction.md b/content/operate/iris/agent-playbook/self-managed/extraction.md index 1e8dddf268..e5dc24c768 100644 --- a/content/operate/iris/agent-playbook/self-managed/extraction.md +++ b/content/operate/iris/agent-playbook/self-managed/extraction.md @@ -107,7 +107,7 @@ Upgrade the release: ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.1 \ + --version '~1.0.1' \ --namespace \ -f iris-values.yaml kubectl -n rollout status deployment/redis-agent-playbook-worker diff --git a/content/operate/iris/agent-playbook/self-managed/prerequisites.md b/content/operate/iris/agent-playbook/self-managed/prerequisites.md index 5237a707a0..1372a5cb8f 100644 --- a/content/operate/iris/agent-playbook/self-managed/prerequisites.md +++ b/content/operate/iris/agent-playbook/self-managed/prerequisites.md @@ -11,7 +11,7 @@ weight: 20 hideListLinks: true --- -The `redis-iris` chart `1.0.1` deploys the Agent Playbooks control plane, data plane, and optional extraction worker, with the Identity Service. Start with the suite's [prerequisites](/content/operate/iris/self-managed/_index.md#prerequisites). This page lists what Agent Playbooks adds: the Redis databases, the embedding provider, and Kubernetes exposure. +The `redis-iris` chart `1.0` deploys the Agent Playbooks control plane, data plane, and optional extraction worker, with the Identity Service. Start with the suite's [prerequisites](/content/operate/iris/self-managed/_index.md#prerequisites). This page lists what Agent Playbooks adds: the Redis databases, the embedding provider, and Kubernetes exposure. ## What you need @@ -75,12 +75,12 @@ The Identity Service's metadata Redis is a suite prerequisite. It can use the Ag ## Images and network access -The suite chart pins these images: +The suite chart pins these images, tagged with the chart version: | Component | Image | | --- | --- | -| Control plane | `redislabs/iris-agent-playbook-control:1.0.1` | -| Data plane and extraction worker | `redislabs/iris-agent-playbook-data:1.0.1` | +| Control plane | `redislabs/iris-agent-playbook-control` | +| Data plane and extraction worker | `redislabs/iris-agent-playbook-data` | Allow chart downloads, image pulls, Redis connections, and data-plane access to the embedding provider. The data plane and control plane must reach the Identity Service, and the Identity Service must reach the control plane on port `9200`. For a disconnected installation, mirror the images, use a downloaded chart package, and set the image repositories and `imagePullSecrets` under `playbook:` in `iris-values.yaml`. diff --git a/content/operate/iris/context-gateway/self-managed/_index.md b/content/operate/iris/context-gateway/self-managed/_index.md index e2afda12c5..aee0731d6d 100644 --- a/content/operate/iris/context-gateway/self-managed/_index.md +++ b/content/operate/iris/context-gateway/self-managed/_index.md @@ -13,7 +13,7 @@ aliases: - /operate/iris/context-retriever/self-managed/ --- -The `redis-iris` chart `1.0.1` deploys the Context Gateway Control Plane and Data Plane, with the Identity Service that issues and checks agent keys. Context Gateway values go under the `contextGateway:` key, and the chart's `examples/context-gateway.yaml` is a working values file to start from. You provide the Redis databases, the `https://` origin MCP clients reach the Data Plane at, and the suite license. The chart doesn't install Redis, Vault, or Secrets Store CSI (Container Storage Interface) Driver resources. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/context-gateway/self-managed/deploy.md). +The `redis-iris` chart `1.0` deploys the Context Gateway Control Plane and Data Plane, with the Identity Service that issues and checks agent keys. Context Gateway values go under the `contextGateway:` key, and the chart's `examples/context-gateway.yaml` is a working values file to start from. You provide the Redis databases, the `https://` origin MCP clients reach the Data Plane at, and the suite license. The chart doesn't install Redis, Vault, or Secrets Store CSI (Container Storage Interface) Driver resources. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/context-gateway/self-managed/deploy.md). Agents call the Data Plane's Model Context Protocol (MCP) endpoint, described in the [MCP API Reference](/content/develop/ai/context-engine/context-gateway/api-reference.md). The [Control Plane API Reference](/content/operate/iris/context-gateway/self-managed/control-plane-api-reference.md) documents the self-managed administration endpoints for Gateways and Upstreams. diff --git a/content/operate/iris/context-gateway/self-managed/deploy.md b/content/operate/iris/context-gateway/self-managed/deploy.md index 64b76348f9..9647a45f7b 100644 --- a/content/operate/iris/context-gateway/self-managed/deploy.md +++ b/content/operate/iris/context-gateway/self-managed/deploy.md @@ -89,7 +89,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.1 \ + --version '~1.0.1' \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/context-gateway/self-managed/prerequisites.md b/content/operate/iris/context-gateway/self-managed/prerequisites.md index 7f700894ed..82717def06 100644 --- a/content/operate/iris/context-gateway/self-managed/prerequisites.md +++ b/content/operate/iris/context-gateway/self-managed/prerequisites.md @@ -110,7 +110,7 @@ Redis URLs, tokens, keyrings, and the license belong in Kubernetes Secrets or Se The chart defaults to these repositories and pins the image tags that match its chart version. Leave `image.repository` and `image.tag` unset for a public install, and override them only to pull from a mirror. -Chart `1.0.1` pins both images to tag `1.0.1`. +The chart pins both images to its own version. ## Air-gapped and private registry installs diff --git a/content/operate/iris/context-gateway/self-managed/reference.md b/content/operate/iris/context-gateway/self-managed/reference.md index 6fb1983ce2..e7f4fd374d 100644 --- a/content/operate/iris/context-gateway/self-managed/reference.md +++ b/content/operate/iris/context-gateway/self-managed/reference.md @@ -58,6 +58,6 @@ Each file reference accepts a Kubernetes Secret or a Secrets Store Container Sto | Need | Reference | | --- | --- | -| Helm chart values | `helm show values redis-ai/redis-iris --version 1.0.1`, with Context Gateway under `contextGateway:` | +| Helm chart values | `helm show values redis-ai/redis-iris --version '~1.0.1'`, with Context Gateway under `contextGateway:` | | Chart examples | `examples/context-gateway.yaml` in the `redis-iris` chart package | -| Chart README | `helm show readme redis-ai/redis-iris --version 1.0.1` | +| Chart README | `helm show readme redis-ai/redis-iris --version '~1.0.1'` | diff --git a/content/operate/iris/identity-service/self-managed/_index.md b/content/operate/iris/identity-service/self-managed/_index.md index 2b28fd7382..08441a1683 100644 --- a/content/operate/iris/identity-service/self-managed/_index.md +++ b/content/operate/iris/identity-service/self-managed/_index.md @@ -17,7 +17,7 @@ The Identity Service is the one place where a self-managed Redis Iris installati 1. It keeps the grants of each key. A grant says which resource the caller can use, and how. 1. It answers the data planes when they ask whether a key is valid, and what it can do. -This guide is for the platform administrator who installs the Identity Service, manages agent keys, and manages operator access. The `redis-iris` chart `1.0.1` always installs the Identity Service, as `iris-identity-service`. Its values go under the `identityService:` key, with the shared values under `global.iris`. It needs no license of its own, because the suite license covers it. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/identity-service/self-managed/deploy.md). +This guide is for the platform administrator who installs the Identity Service, manages agent keys, and manages operator access. The `redis-iris` chart `1.0` always installs the Identity Service, as `iris-identity-service`. Its values go under the `identityService:` key, with the shared values under `global.iris`. It needs no license of its own, because the suite license covers it. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/identity-service/self-managed/deploy.md). ## What you deploy diff --git a/content/operate/iris/identity-service/self-managed/deploy.md b/content/operate/iris/identity-service/self-managed/deploy.md index c21c2bfa09..0d3ebd2883 100644 --- a/content/operate/iris/identity-service/self-managed/deploy.md +++ b/content/operate/iris/identity-service/self-managed/deploy.md @@ -73,9 +73,9 @@ Run the [suite preflight](/content/operate/iris/self-managed/_index.md#4-run-the ```bash helm repo add redis-ai https://helm.redis.io/ai helm repo update redis-ai -helm pull redis-ai/redis-iris --version 1.0.1 --untar +helm pull redis-ai/redis-iris --version '~1.0.1' --untar helm install iris redis-ai/redis-iris \ - --version 1.0.1 \ + --version '~1.0.1' \ --namespace \ -f redis-iris/examples/memory-only.yaml \ -f iris-values.yaml diff --git a/content/operate/iris/identity-service/self-managed/prerequisites.md b/content/operate/iris/identity-service/self-managed/prerequisites.md index f0b61f34d3..1cd581fe01 100644 --- a/content/operate/iris/identity-service/self-managed/prerequisites.md +++ b/content/operate/iris/identity-service/self-managed/prerequisites.md @@ -17,7 +17,7 @@ The Identity Service depends on a metadata Redis and Secrets that you set up fir | Requirement | Detail | | --- | --- | -| Suite chart | `redis-iris` chart `1.0.1` in the Redis AI Helm repository, `https://helm.redis.io/ai`. The suite prerequisites list the Kubernetes, Helm, and Metrics API versions. | +| Suite chart | `redis-iris` chart `1.0` in the Redis AI Helm repository, `https://helm.redis.io/ai`. The suite prerequisites list the Kubernetes, Helm, and Metrics API versions. | | Namespace | A namespace that holds only this release. The examples use ``. | | Metadata Redis | A Redis database for the Identity Service, as described in [Metadata Redis](#metadata-redis). | | `kubectl`, `curl` | For the install and administration examples. | diff --git a/content/operate/iris/intent-router/self-managed/_index.md b/content/operate/iris/intent-router/self-managed/_index.md index 6ab53482e7..c821107ba1 100644 --- a/content/operate/iris/intent-router/self-managed/_index.md +++ b/content/operate/iris/intent-router/self-managed/_index.md @@ -15,7 +15,7 @@ Intent Router classifies each incoming user message by intent, so your applicati This guide is for that administrator. It covers deploying Intent Router on your own Kubernetes cluster, then configuring, securing, and operating it. To install, follow [Install the Redis Iris suite](/content/operate/iris/self-managed/_index.md), then [Deploy](/content/operate/iris/intent-router/self-managed/deploy.md). -The `redis-iris` chart `1.0.1` deploys the Intent Router control plane and data plane, with the Identity Service that issues and checks agent keys. Intent Router values go under the `intent:` key, and the chart's `examples/intent.yaml` is a working values file to start from. You provide the Redis databases, the embedding provider credentials, and the suite license. +The `redis-iris` chart `1.0` deploys the Intent Router control plane and data plane, with the Identity Service that issues and checks agent keys. Intent Router values go under the `intent:` key, and the chart's `examples/intent.yaml` is a working values file to start from. You provide the Redis databases, the embedding provider credentials, and the suite license. Applications call the data plane to author intents and match queries, as described in the [data-plane API reference](/content/develop/ai/context-engine/intent-router/api-reference.md). The [control-plane API reference](/content/operate/iris/intent-router/self-managed/control-plane-api-reference.md) documents the administration endpoints for Routers. diff --git a/content/operate/iris/intent-router/self-managed/deploy.md b/content/operate/iris/intent-router/self-managed/deploy.md index ee1f7fec00..962702d263 100644 --- a/content/operate/iris/intent-router/self-managed/deploy.md +++ b/content/operate/iris/intent-router/self-managed/deploy.md @@ -70,7 +70,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.1 \ + --version '~1.0.1' \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/lens/self-managed/_index.md b/content/operate/iris/lens/self-managed/_index.md index f5a3cc1659..41ed34b2a6 100644 --- a/content/operate/iris/lens/self-managed/_index.md +++ b/content/operate/iris/lens/self-managed/_index.md @@ -17,7 +17,7 @@ This guide is for that administrator. It covers deploying Lens on your own Kuber ## What you deploy -The `redis-iris` chart `1.0.1` runs three Lens workloads, with the Identity Service. Lens values go under the `lens:` key, and the chart's `examples/lens.yaml` is a working values file to start from. +The `redis-iris` chart `1.0` runs three Lens workloads, with the Identity Service. Lens values go under the `lens:` key, and the chart's `examples/lens.yaml` is a working values file to start from. | Component | Purpose | Service port | | --- | --- | --- | diff --git a/content/operate/iris/lens/self-managed/deploy.md b/content/operate/iris/lens/self-managed/deploy.md index 79a75e11da..04e2c6e33b 100644 --- a/content/operate/iris/lens/self-managed/deploy.md +++ b/content/operate/iris/lens/self-managed/deploy.md @@ -52,7 +52,7 @@ For a new release, follow [Run the preflight](/content/operate/iris/self-managed ```bash helm upgrade iris redis-ai/redis-iris \ - --version 1.0.1 \ + --version '~1.0.1' \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/lens/self-managed/prerequisites.md b/content/operate/iris/lens/self-managed/prerequisites.md index df11b0a301..49b6c0d010 100644 --- a/content/operate/iris/lens/self-managed/prerequisites.md +++ b/content/operate/iris/lens/self-managed/prerequisites.md @@ -23,7 +23,7 @@ Self-managed Lens runs on your Kubernetes cluster as part of the `redis-iris` su | Identity Service | Installed by the suite, as `iris-identity-service`. | | Redis databases | A records database, a content database, and a metadata Redis, as described in [Redis databases](#redis-databases). | | Container images | Docker Hub: `redislabs/iris-lens-data` (data plane and worker) and `redislabs/iris-lens-control` (control plane). | -| Helm chart | `redis-iris` chart `1.0.1` in the Redis AI Helm repository, `https://helm.redis.io/ai`. | +| Helm chart | `redis-iris` chart `1.0` in the Redis AI Helm repository, `https://helm.redis.io/ai`. | | License key | The suite license. Contact your Redis representative or [contact sales](https://redis.io/contact/). | ## Redis databases diff --git a/content/operate/iris/self-managed/_index.md b/content/operate/iris/self-managed/_index.md index 715e13f081..2a09d85759 100644 --- a/content/operate/iris/self-managed/_index.md +++ b/content/operate/iris/self-managed/_index.md @@ -40,7 +40,7 @@ Install one release per namespace, and keep other Iris releases out of that name | Requirement | Details | | --- | --- | | Kubernetes | Kubernetes 1.28 or later. The baseline is 3 worker nodes with 12 vCPU and 24 GiB allocatable in total. The [preflight](#4-run-the-preflight) warns below it. | -| Node architecture | `linux/amd64` or `linux/arm64`. Each `1.0.1` image tag is one multi-platform image, so every node pulls its own. The `1.0.0` images are `amd64` only. | +| Node architecture | `linux/amd64` or `linux/arm64`. From `1.0.1`, each image tag is one multi-platform image, so every node pulls its own. The `1.0.0` images are `amd64` only. | | Metrics API | `metrics.k8s.io/v1beta1`, so the HorizontalPodAutoscalers can scale. | | Helm | Helm 3.10 or later, with the Redis AI repository `https://helm.redis.io/ai`. Helm 4 isn't supported in this release. | | `kubectl` | Configured for the cluster and namespace. | @@ -163,7 +163,7 @@ ui: Every service is installed by default. Turn one off with `global.iris.products..enabled: false`, where `` is `memory`, `playbook`, `lens`, `contextGateway`, or `intent`. The chart's `examples/` folder has one values file per service, which you can pass as extra `-f` files: ```bash -helm pull redis-ai/redis-iris --version 1.0.1 --untar +helm pull redis-ai/redis-iris --version '~1.0.1' --untar ls redis-iris/examples ``` @@ -205,7 +205,7 @@ The chart includes a preflight that checks the cluster before an install. It rea Run it with the [`kubectl preflight`](https://troubleshoot.sh/docs/#installation) plugin, v0.124.0 or later. Older versions only warn on the ingress class check. The namespace must exist: ```bash -helm template iris redis-ai/redis-iris --version 1.0.1 -n -f iris-values.yaml \ +helm template iris redis-ai/redis-iris --version '~1.0.1' -n -f iris-values.yaml \ --show-only templates/preflight.yaml \ | yq '.stringData["preflight.yaml"]' | kubectl preflight - ``` @@ -231,7 +231,7 @@ kubectl create clusterrolebinding -issuer-discovery \ helm repo add redis-ai https://helm.redis.io/ai helm repo update redis-ai helm install iris redis-ai/redis-iris \ - --version 1.0.1 \ + --version '~1.0.1' \ --namespace \ -f iris-values.yaml ``` diff --git a/content/operate/iris/self-managed/operations.md b/content/operate/iris/self-managed/operations.md index a4945b98e4..5801926ade 100644 --- a/content/operate/iris/self-managed/operations.md +++ b/content/operate/iris/self-managed/operations.md @@ -62,7 +62,7 @@ helm rollback iris --namespace --wait --timeout 15m A rollback restores the workloads and the values of that revision. It doesn't undo data or metadata written to Redis. It never restores a credential: the generated Secrets aren't part of the release, so a rotated or revoked value stays rotated or revoked. The same version rules as for an upgrade apply. You can't roll back to `1.0.0` on `arm64` nodes, because its images are `amd64` only. -Keep the chart of each version you install, so you can roll back without the repository: +Keep the chart of each version you install, so you can roll back without the repository. `helm list --namespace ` shows the installed version: ```bash helm pull redis-ai/redis-iris --version