diff --git a/content/docs/2.0/scalers/redis-lists.md b/content/docs/2.0/scalers/redis-lists.md
index 28755fd12..bb0493604 100644
--- a/content/docs/2.0/scalers/redis-lists.md
+++ b/content/docs/2.0/scalers/redis-lists.md
@@ -37,6 +37,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.0/scalers/redis-streams.md b/content/docs/2.0/scalers/redis-streams.md
index b77700d5b..49d685585 100644
--- a/content/docs/2.0/scalers/redis-streams.md
+++ b/content/docs/2.0/scalers/redis-streams.md
@@ -56,6 +56,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.1/scalers/redis-cluster-lists.md b/content/docs/2.1/scalers/redis-cluster-lists.md
index f70c47894..882f9cc79 100644
--- a/content/docs/2.1/scalers/redis-cluster-lists.md
+++ b/content/docs/2.1/scalers/redis-cluster-lists.md
@@ -35,6 +35,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.1/scalers/redis-cluster-streams.md b/content/docs/2.1/scalers/redis-cluster-streams.md
index ead5ef7f7..b765be684 100644
--- a/content/docs/2.1/scalers/redis-cluster-streams.md
+++ b/content/docs/2.1/scalers/redis-cluster-streams.md
@@ -54,6 +54,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Cluster nodes. The resolved hosts should follow a format like `node1:6379, node2:6379, node3:6379 ...`.
diff --git a/content/docs/2.1/scalers/redis-lists.md b/content/docs/2.1/scalers/redis-lists.md
index 28755fd12..bb0493604 100644
--- a/content/docs/2.1/scalers/redis-lists.md
+++ b/content/docs/2.1/scalers/redis-lists.md
@@ -37,6 +37,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.1/scalers/redis-streams.md b/content/docs/2.1/scalers/redis-streams.md
index b77700d5b..49d685585 100644
--- a/content/docs/2.1/scalers/redis-streams.md
+++ b/content/docs/2.1/scalers/redis-streams.md
@@ -56,6 +56,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.10/scalers/loki.md b/content/docs/2.10/scalers/loki.md
index 95cb7b51d..a9423e82d 100644
--- a/content/docs/2.10/scalers/loki.md
+++ b/content/docs/2.10/scalers/loki.md
@@ -22,7 +22,7 @@ triggers:
     activationThreshold: '2.50'
     tenantName: Tenant1 # Optional. X-Scope-OrgID header for specifying the tenant name in a multi-tenant setup.
     ignoreNullValues: false # Default is `true`, which means ignoring the empty value list from Loki. Set to `false` the scaler will return error when Loki target is lost
-    unsafeSsl: false #  Default is `false`, Used for skipping certificate check when having self signed certs for Loki endpoint
+    unsafeSsl: "false" #  Default is `false`, Used for skipping certificate check when having self signed certs for Loki endpoint
 ```
 
 **Parameter list:**
diff --git a/content/docs/2.10/scalers/prometheus.md b/content/docs/2.10/scalers/prometheus.md
index 1b6fbf30c..eb3849469 100644
--- a/content/docs/2.10/scalers/prometheus.md
+++ b/content/docs/2.10/scalers/prometheus.md
@@ -24,7 +24,7 @@ triggers:
     namespace: example-namespace  # for namespaced queries, eg. Thanos
     cortexOrgID: my-org # Optional. X-Scope-OrgID header for Cortex.
     ignoreNullValues: false # Default is `true`, which means ignoring the empty value list from Prometheus. Set to `false` the scaler will return error when Prometheus target is lost
-    unsafeSsl: false #  Default is `false`, Used for skipping certificate check when having self signed certs for Prometheus endpoint
+    unsafeSsl: "false" #  Default is `false`, Used for skipping certificate check when having self signed certs for Prometheus endpoint
 ```
 
 **Parameter list:**
diff --git a/content/docs/2.10/scalers/redis-cluster-lists.md b/content/docs/2.10/scalers/redis-cluster-lists.md
index 6dfd26222..98983c6d6 100644
--- a/content/docs/2.10/scalers/redis-cluster-lists.md
+++ b/content/docs/2.10/scalers/redis-cluster-lists.md
@@ -21,6 +21,7 @@ triggers:
     listLength: "5" # Required
     activationListLength: "5" # optional
     enableTLS: "false" # optional
+    unsafeSsl: "false" # optional
     # Alternatively, you can use existing environment variables to read configuration from:
     # See details in "Parameter list" section
     addressesFromEnv: REDIS_ADDRESSES # Optional. You can use this instead of `addresses` parameter
@@ -38,6 +39,7 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `activationListLength` - Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds).(Default: `0`, Optional)
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
+- `unsafeSsl` - Used for skipping certificate check e.g: using self signed certs. (Values: `true`,`false`, Default: `false`, Optional, This requires `enableTLS: true`)
 
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
diff --git a/content/docs/2.10/scalers/redis-cluster-streams.md b/content/docs/2.10/scalers/redis-cluster-streams.md
index bd281f858..98c1073e9 100644
--- a/content/docs/2.10/scalers/redis-cluster-streams.md
+++ b/content/docs/2.10/scalers/redis-cluster-streams.md
@@ -28,6 +28,7 @@ triggers:
     consumerGroup: my-consumer-group # Required - name of consumer group associated with Redis Stream
     pendingEntriesCount: "10" # Required - number of entries in the Pending Entries List for the specified consumer group in the Redis Stream
     enableTLS: "false" # optional
+    unsafeSsl: "false" # optional
     # Alternatively, you can use existing environment variables to read configuration from:
     # See details in "Parameter list" section
     addressesFromEnv: REDIS_ADDRESSES # Optional. You can use this instead of `addresses` parameter
@@ -56,6 +57,7 @@ triggers:
 - `consumerGroup` - Name of the Consumer group associated with Redis Stream.
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
+- `unsafeSsl` - Used for skipping certificate check e.g: using self signed certs. (Values: `true`,`false`, Default: `false`, Optional, This requires `enableTLS: true`)
 
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
diff --git a/content/docs/2.10/scalers/redis-lists.md b/content/docs/2.10/scalers/redis-lists.md
index 6e99cf312..9326fe4ee 100644
--- a/content/docs/2.10/scalers/redis-lists.md
+++ b/content/docs/2.10/scalers/redis-lists.md
@@ -21,6 +21,7 @@ triggers:
     listLength: "5" # Required
     activationListLength: "5" # optional
     enableTLS: "false" # optional
+    unsafeSsl: "false" # optional
     databaseIndex: "0" # optional
     # Alternatively, you can use existing environment variables to read configuration from:
     # See details in "Parameter list" section
@@ -39,6 +40,7 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `activationListLength` - Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds).(Default: `0`, Optional)
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
+- `unsafeSsl` - Used for skipping certificate check e.g: using self signed certs. (Values: `true`,`false`, Default: `false`, Optional, This requires `enableTLS: true`)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
diff --git a/content/docs/2.10/scalers/redis-sentinel-lists.md b/content/docs/2.10/scalers/redis-sentinel-lists.md
index 34a82d9fa..dc02ee5d6 100644
--- a/content/docs/2.10/scalers/redis-sentinel-lists.md
+++ b/content/docs/2.10/scalers/redis-sentinel-lists.md
@@ -24,6 +24,7 @@ triggers:
     listLength: "5" # Required
     activationListLength: "5" # optional
     enableTLS: "false" # optional
+    unsafeSsl: "false" # optional
     # Alternatively, you can use existing environment variables to read configuration from:
     # See details in "Parameter list" section
     addressesFromEnv: REDIS_ADDRESSES # Optional. You can use this instead of `addresses` parameter
@@ -44,6 +45,7 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `activationListLength` - Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds).(Default: `0`, Optional)
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
+- `unsafeSsl` - Used for skipping certificate check e.g: using self signed certs. (Values: `true`,`false`, Default: `false`, Optional, This requires `enableTLS: true`)
 
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
diff --git a/content/docs/2.10/scalers/redis-sentinel-streams.md b/content/docs/2.10/scalers/redis-sentinel-streams.md
index d91e979bb..406675ceb 100644
--- a/content/docs/2.10/scalers/redis-sentinel-streams.md
+++ b/content/docs/2.10/scalers/redis-sentinel-streams.md
@@ -28,6 +28,7 @@ triggers:
     consumerGroup: my-consumer-group # Required - name of consumer group associated with Redis Stream
     pendingEntriesCount: "10" # Required - number of entries in the Pending Entries List for the specified consumer group in the Redis Stream
     enableTLS: "false" # optional
+    unsafeSsl: "false" # optional
     # Alternatively, you can use existing environment variables to read configuration from:
     # See details in "Parameter list" section
     addressesFromEnv: REDIS_ADDRESSES # Optional. You can use this instead of `addresses` parameter
@@ -60,6 +61,7 @@ triggers:
 - `consumerGroup` - Name of the Consumer group associated with Redis Stream.
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
+- `unsafeSsl` - Used for skipping certificate check e.g: using self signed certs. (Values: `true`,`false`, Default: `false`, Optional, This requires `enableTLS: true`)
 
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
diff --git a/content/docs/2.10/scalers/redis-streams.md b/content/docs/2.10/scalers/redis-streams.md
index d47a26c44..4fbe88c73 100644
--- a/content/docs/2.10/scalers/redis-streams.md
+++ b/content/docs/2.10/scalers/redis-streams.md
@@ -28,6 +28,7 @@ triggers:
     consumerGroup: my-consumer-group # Required - name of consumer group associated with Redis Stream
     pendingEntriesCount: "10" # Required - number of entries in the Pending Entries List for the specified consumer group in the Redis Stream
     enableTLS: "false" # optional
+    unsafeSsl: "false" # optional
     databaseIndex: "0" # optional
     # Alternatively, you can use existing environment variables to read configuration from:
     # See details in "Parameter list" section
@@ -58,6 +59,7 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
+- `unsafeSsl` - Used for skipping certificate check e.g: using self signed certs. (Values: `true`,`false`, Default: `false`, Optional, This requires `enableTLS: true`)
 
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
diff --git a/content/docs/2.2/scalers/redis-cluster-lists.md b/content/docs/2.2/scalers/redis-cluster-lists.md
index f70c47894..882f9cc79 100644
--- a/content/docs/2.2/scalers/redis-cluster-lists.md
+++ b/content/docs/2.2/scalers/redis-cluster-lists.md
@@ -35,6 +35,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.2/scalers/redis-cluster-streams.md b/content/docs/2.2/scalers/redis-cluster-streams.md
index ead5ef7f7..b765be684 100644
--- a/content/docs/2.2/scalers/redis-cluster-streams.md
+++ b/content/docs/2.2/scalers/redis-cluster-streams.md
@@ -54,6 +54,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Cluster nodes. The resolved hosts should follow a format like `node1:6379, node2:6379, node3:6379 ...`.
diff --git a/content/docs/2.2/scalers/redis-lists.md b/content/docs/2.2/scalers/redis-lists.md
index 28755fd12..bb0493604 100644
--- a/content/docs/2.2/scalers/redis-lists.md
+++ b/content/docs/2.2/scalers/redis-lists.md
@@ -37,6 +37,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.2/scalers/redis-streams.md b/content/docs/2.2/scalers/redis-streams.md
index b77700d5b..49d685585 100644
--- a/content/docs/2.2/scalers/redis-streams.md
+++ b/content/docs/2.2/scalers/redis-streams.md
@@ -56,6 +56,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.3/scalers/redis-cluster-lists.md b/content/docs/2.3/scalers/redis-cluster-lists.md
index f70c47894..882f9cc79 100644
--- a/content/docs/2.3/scalers/redis-cluster-lists.md
+++ b/content/docs/2.3/scalers/redis-cluster-lists.md
@@ -35,6 +35,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.3/scalers/redis-cluster-streams.md b/content/docs/2.3/scalers/redis-cluster-streams.md
index ead5ef7f7..b765be684 100644
--- a/content/docs/2.3/scalers/redis-cluster-streams.md
+++ b/content/docs/2.3/scalers/redis-cluster-streams.md
@@ -54,6 +54,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Cluster nodes. The resolved hosts should follow a format like `node1:6379, node2:6379, node3:6379 ...`.
diff --git a/content/docs/2.3/scalers/redis-lists.md b/content/docs/2.3/scalers/redis-lists.md
index 28755fd12..bb0493604 100644
--- a/content/docs/2.3/scalers/redis-lists.md
+++ b/content/docs/2.3/scalers/redis-lists.md
@@ -37,6 +37,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.3/scalers/redis-streams.md b/content/docs/2.3/scalers/redis-streams.md
index b77700d5b..49d685585 100644
--- a/content/docs/2.3/scalers/redis-streams.md
+++ b/content/docs/2.3/scalers/redis-streams.md
@@ -56,6 +56,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.4/scalers/redis-cluster-lists.md b/content/docs/2.4/scalers/redis-cluster-lists.md
index f70c47894..882f9cc79 100644
--- a/content/docs/2.4/scalers/redis-cluster-lists.md
+++ b/content/docs/2.4/scalers/redis-cluster-lists.md
@@ -35,6 +35,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.4/scalers/redis-cluster-streams.md b/content/docs/2.4/scalers/redis-cluster-streams.md
index ead5ef7f7..b765be684 100644
--- a/content/docs/2.4/scalers/redis-cluster-streams.md
+++ b/content/docs/2.4/scalers/redis-cluster-streams.md
@@ -54,6 +54,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Cluster nodes. The resolved hosts should follow a format like `node1:6379, node2:6379, node3:6379 ...`.
diff --git a/content/docs/2.4/scalers/redis-lists.md b/content/docs/2.4/scalers/redis-lists.md
index 28755fd12..bb0493604 100644
--- a/content/docs/2.4/scalers/redis-lists.md
+++ b/content/docs/2.4/scalers/redis-lists.md
@@ -37,6 +37,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.4/scalers/redis-streams.md b/content/docs/2.4/scalers/redis-streams.md
index b77700d5b..49d685585 100644
--- a/content/docs/2.4/scalers/redis-streams.md
+++ b/content/docs/2.4/scalers/redis-streams.md
@@ -56,6 +56,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.5/scalers/redis-cluster-lists.md b/content/docs/2.5/scalers/redis-cluster-lists.md
index 66c5b9e7c..198448d0e 100644
--- a/content/docs/2.5/scalers/redis-cluster-lists.md
+++ b/content/docs/2.5/scalers/redis-cluster-lists.md
@@ -37,6 +37,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.5/scalers/redis-cluster-streams.md b/content/docs/2.5/scalers/redis-cluster-streams.md
index bd281f858..6ca3f8a2d 100644
--- a/content/docs/2.5/scalers/redis-cluster-streams.md
+++ b/content/docs/2.5/scalers/redis-cluster-streams.md
@@ -57,6 +57,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Cluster nodes. The resolved hosts should follow a format like `node1:6379, node2:6379, node3:6379 ...`.
diff --git a/content/docs/2.5/scalers/redis-lists.md b/content/docs/2.5/scalers/redis-lists.md
index 1fcdc4a35..a3e1ea19b 100644
--- a/content/docs/2.5/scalers/redis-lists.md
+++ b/content/docs/2.5/scalers/redis-lists.md
@@ -39,6 +39,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.5/scalers/redis-sentinel-lists.md b/content/docs/2.5/scalers/redis-sentinel-lists.md
index 051371368..c209165e2 100644
--- a/content/docs/2.5/scalers/redis-sentinel-lists.md
+++ b/content/docs/2.5/scalers/redis-sentinel-lists.md
@@ -43,6 +43,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Sentinel nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.5/scalers/redis-sentinel-streams.md b/content/docs/2.5/scalers/redis-sentinel-streams.md
index d91e979bb..22090eeba 100644
--- a/content/docs/2.5/scalers/redis-sentinel-streams.md
+++ b/content/docs/2.5/scalers/redis-sentinel-streams.md
@@ -61,6 +61,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Sentinel nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Sentinel nodes. The resolved hosts should follow a format like `node1:26379, node2:26379, node3:26379 ...`.
diff --git a/content/docs/2.5/scalers/redis-streams.md b/content/docs/2.5/scalers/redis-streams.md
index d47a26c44..056ebcb01 100644
--- a/content/docs/2.5/scalers/redis-streams.md
+++ b/content/docs/2.5/scalers/redis-streams.md
@@ -59,6 +59,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.6/scalers/redis-cluster-lists.md b/content/docs/2.6/scalers/redis-cluster-lists.md
index 66c5b9e7c..198448d0e 100644
--- a/content/docs/2.6/scalers/redis-cluster-lists.md
+++ b/content/docs/2.6/scalers/redis-cluster-lists.md
@@ -37,6 +37,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.6/scalers/redis-cluster-streams.md b/content/docs/2.6/scalers/redis-cluster-streams.md
index bd281f858..6ca3f8a2d 100644
--- a/content/docs/2.6/scalers/redis-cluster-streams.md
+++ b/content/docs/2.6/scalers/redis-cluster-streams.md
@@ -57,6 +57,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Cluster nodes. The resolved hosts should follow a format like `node1:6379, node2:6379, node3:6379 ...`.
diff --git a/content/docs/2.6/scalers/redis-lists.md b/content/docs/2.6/scalers/redis-lists.md
index 1fcdc4a35..a3e1ea19b 100644
--- a/content/docs/2.6/scalers/redis-lists.md
+++ b/content/docs/2.6/scalers/redis-lists.md
@@ -39,6 +39,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.6/scalers/redis-sentinel-lists.md b/content/docs/2.6/scalers/redis-sentinel-lists.md
index 051371368..c209165e2 100644
--- a/content/docs/2.6/scalers/redis-sentinel-lists.md
+++ b/content/docs/2.6/scalers/redis-sentinel-lists.md
@@ -43,6 +43,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Sentinel nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.6/scalers/redis-sentinel-streams.md b/content/docs/2.6/scalers/redis-sentinel-streams.md
index d91e979bb..22090eeba 100644
--- a/content/docs/2.6/scalers/redis-sentinel-streams.md
+++ b/content/docs/2.6/scalers/redis-sentinel-streams.md
@@ -61,6 +61,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Sentinel nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Sentinel nodes. The resolved hosts should follow a format like `node1:26379, node2:26379, node3:26379 ...`.
diff --git a/content/docs/2.6/scalers/redis-streams.md b/content/docs/2.6/scalers/redis-streams.md
index d47a26c44..056ebcb01 100644
--- a/content/docs/2.6/scalers/redis-streams.md
+++ b/content/docs/2.6/scalers/redis-streams.md
@@ -59,6 +59,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.7/scalers/redis-cluster-lists.md b/content/docs/2.7/scalers/redis-cluster-lists.md
index 66c5b9e7c..198448d0e 100644
--- a/content/docs/2.7/scalers/redis-cluster-lists.md
+++ b/content/docs/2.7/scalers/redis-cluster-lists.md
@@ -37,6 +37,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.7/scalers/redis-cluster-streams.md b/content/docs/2.7/scalers/redis-cluster-streams.md
index bd281f858..6ca3f8a2d 100644
--- a/content/docs/2.7/scalers/redis-cluster-streams.md
+++ b/content/docs/2.7/scalers/redis-cluster-streams.md
@@ -57,6 +57,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Cluster nodes. The resolved hosts should follow a format like `node1:6379, node2:6379, node3:6379 ...`.
diff --git a/content/docs/2.7/scalers/redis-lists.md b/content/docs/2.7/scalers/redis-lists.md
index 1fcdc4a35..a3e1ea19b 100644
--- a/content/docs/2.7/scalers/redis-lists.md
+++ b/content/docs/2.7/scalers/redis-lists.md
@@ -39,6 +39,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.7/scalers/redis-sentinel-lists.md b/content/docs/2.7/scalers/redis-sentinel-lists.md
index 051371368..c209165e2 100644
--- a/content/docs/2.7/scalers/redis-sentinel-lists.md
+++ b/content/docs/2.7/scalers/redis-sentinel-lists.md
@@ -43,6 +43,8 @@ triggers:
 - `listLength` - Average target value to trigger scaling actions.
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Sentinel nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.7/scalers/redis-sentinel-streams.md b/content/docs/2.7/scalers/redis-sentinel-streams.md
index d91e979bb..22090eeba 100644
--- a/content/docs/2.7/scalers/redis-sentinel-streams.md
+++ b/content/docs/2.7/scalers/redis-sentinel-streams.md
@@ -61,6 +61,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Sentinel nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Sentinel nodes. The resolved hosts should follow a format like `node1:26379, node2:26379, node3:26379 ...`.
diff --git a/content/docs/2.7/scalers/redis-streams.md b/content/docs/2.7/scalers/redis-streams.md
index d47a26c44..056ebcb01 100644
--- a/content/docs/2.7/scalers/redis-streams.md
+++ b/content/docs/2.7/scalers/redis-streams.md
@@ -59,6 +59,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.8/scalers/redis-cluster-lists.md b/content/docs/2.8/scalers/redis-cluster-lists.md
index 6dfd26222..592094dfa 100644
--- a/content/docs/2.8/scalers/redis-cluster-lists.md
+++ b/content/docs/2.8/scalers/redis-cluster-lists.md
@@ -39,6 +39,8 @@ triggers:
 - `activationListLength` - Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds).(Default: `0`, Optional)
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.8/scalers/redis-cluster-streams.md b/content/docs/2.8/scalers/redis-cluster-streams.md
index bd281f858..6ca3f8a2d 100644
--- a/content/docs/2.8/scalers/redis-cluster-streams.md
+++ b/content/docs/2.8/scalers/redis-cluster-streams.md
@@ -57,6 +57,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Cluster nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Cluster nodes. The resolved hosts should follow a format like `node1:6379, node2:6379, node3:6379 ...`.
diff --git a/content/docs/2.8/scalers/redis-lists.md b/content/docs/2.8/scalers/redis-lists.md
index 6e99cf312..98bad827a 100644
--- a/content/docs/2.8/scalers/redis-lists.md
+++ b/content/docs/2.8/scalers/redis-lists.md
@@ -41,6 +41,8 @@ triggers:
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 - `databaseIndex` - Index of Redis database to use. If not specified, the default value is 0.
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.8/scalers/redis-sentinel-lists.md b/content/docs/2.8/scalers/redis-sentinel-lists.md
index 34a82d9fa..e7116b66c 100644
--- a/content/docs/2.8/scalers/redis-sentinel-lists.md
+++ b/content/docs/2.8/scalers/redis-sentinel-lists.md
@@ -45,6 +45,8 @@ triggers:
 - `activationListLength` - Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds).(Default: `0`, Optional)
 - `enableTLS` - Allow a connection to a redis queue using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and their respective ports of the Redis Sentinel nodes, similar to `addresses`, but reads it from an environment variable on the scale target.
diff --git a/content/docs/2.8/scalers/redis-sentinel-streams.md b/content/docs/2.8/scalers/redis-sentinel-streams.md
index d91e979bb..22090eeba 100644
--- a/content/docs/2.8/scalers/redis-sentinel-streams.md
+++ b/content/docs/2.8/scalers/redis-sentinel-streams.md
@@ -61,6 +61,8 @@ triggers:
 - `pendingEntriesCount` - Threshold for the number of `Pending Entries List`. This is the average target value to scale the workload. (Default: `5`, Optional)
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressesFromEnv` - The hosts and corresponding ports of Redis Sentinel nodes, similar to `addresses`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the URLs of Redis Sentinel nodes. The resolved hosts should follow a format like `node1:26379, node2:26379, node3:26379 ...`.
diff --git a/content/docs/2.8/scalers/redis-streams.md b/content/docs/2.8/scalers/redis-streams.md
index d47a26c44..056ebcb01 100644
--- a/content/docs/2.8/scalers/redis-streams.md
+++ b/content/docs/2.8/scalers/redis-streams.md
@@ -59,6 +59,8 @@ triggers:
 - `databaseIndex` - The Redis database index. Defaults to `0` if not specified.
 - `enableTLS` - Allow a connection to Redis using tls. (Values: `true`, `false`, Default: `false`, Optional)
 
+> ⚠️ **WARNING:** In this version, `enableTLS: true` automatically skips the certificate verification which is insecure. Use v2.9 or above to properly verify the server certificate.
+
 Some parameters could be provided using environmental variables, instead of setting them directly in metadata. Here is a list of parameters you can use to retrieve values from environment variables:
 
 - `addressFromEnv` - The host and port of the Redis server, similar to `address`, but reads it from an environment variable on the scale target. Name of the environment variable your deployment uses to get the Redis server URL. The resolved host should follow a format like `my-redis:6379`.
diff --git a/content/docs/2.9/scalers/loki.md b/content/docs/2.9/scalers/loki.md
index 95cb7b51d..a9423e82d 100644
--- a/content/docs/2.9/scalers/loki.md
+++ b/content/docs/2.9/scalers/loki.md
@@ -22,7 +22,7 @@ triggers:
     activationThreshold: '2.50'
     tenantName: Tenant1 # Optional. X-Scope-OrgID header for specifying the tenant name in a multi-tenant setup.
     ignoreNullValues: false # Default is `true`, which means ignoring the empty value list from Loki. Set to `false` the scaler will return error when Loki target is lost
-    unsafeSsl: false #  Default is `false`, Used for skipping certificate check when having self signed certs for Loki endpoint
+    unsafeSsl: "false" #  Default is `false`, Used for skipping certificate check when having self signed certs for Loki endpoint
 ```
 
 **Parameter list:**
diff --git a/content/docs/2.9/scalers/prometheus.md b/content/docs/2.9/scalers/prometheus.md
index 1b6fbf30c..eb3849469 100644
--- a/content/docs/2.9/scalers/prometheus.md
+++ b/content/docs/2.9/scalers/prometheus.md
@@ -24,7 +24,7 @@ triggers:
     namespace: example-namespace  # for namespaced queries, eg. Thanos
     cortexOrgID: my-org # Optional. X-Scope-OrgID header for Cortex.
     ignoreNullValues: false # Default is `true`, which means ignoring the empty value list from Prometheus. Set to `false` the scaler will return error when Prometheus target is lost
-    unsafeSsl: false #  Default is `false`, Used for skipping certificate check when having self signed certs for Prometheus endpoint
+    unsafeSsl: "false" #  Default is `false`, Used for skipping certificate check when having self signed certs for Prometheus endpoint
 ```
 
 **Parameter list:**