From 59b81d1c5924ff5f3db38d45a2c7ae60c8da776a Mon Sep 17 00:00:00 2001 From: Binbin Li Date: Mon, 20 Jan 2025 13:40:53 +0800 Subject: [PATCH] docs: update dead link (#2040) Signed-off-by: Binbin Li --- docs/discussion/Multi-Tenancy Support.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/discussion/Multi-Tenancy Support.md b/docs/discussion/Multi-Tenancy Support.md index b9c339f33..db972e9d7 100644 --- a/docs/discussion/Multi-Tenancy Support.md +++ b/docs/discussion/Multi-Tenancy Support.md @@ -96,7 +96,7 @@ Ratify can be deployed either per namespace or per cluster. Redis can also be de | | Ratify per Namespace | Ratify per Cluster | |--|--|--| | Redis per Namespace | Data Isolated | It requires Ratify route requests to Redis instances in different namespaces | -| Redis per Cluster | Prefix keys and restrict access via [ACL](https://redis.io/docs/management/security/acl/) | Prefix keys and restrict access via [ACL](https://redis.io/docs/management/security/acl/) | +| Redis per Cluster | Prefix keys and restrict access via [ACL](https://redis.io/docs/latest/operate/oss_and_stack/management/security/acl/) | Prefix keys and restrict access via [ACL](https://redis.io/docs/latest/operate/oss_and_stack/management/security/acl/) | #### Log Ratify saves logs to the standard output and then handled by container runtime. Whatever path does container runtime save logs, those logs may include data from different teams. This situation mirrors the challenges observed with cache isolation.