Merge pull request #11147 from harness/FFM-12550

Add release notes for Proxy 2.0.14 & update docs

Author: alai97

docs/feature-flags/use-ff/relay-proxy/relay_proxy_v2.md renamed to docs/feature-flags/use-ff/relay-proxy/relay-proxy-v2.md

@@ -4,6 +4,7 @@ description: This topic focuses on version 2 of the Relay Proxy, how to use it a
 sidebar_position: 10
 redirect_from:
   - /docs/feature-flags/relay-proxy/relay_proxy_v2
+  - /docs/feature-flags/use-ff/relay-proxy/relay_proxy_v2
 ---
 
 This topic describes the Harness Relay Proxy V2 and how to use it with Feature Flags (FF).
@@ -147,6 +148,20 @@ The below table outlines all of the configuration options that are available for
 | AND_RULES              | true                                 | Enables AND rule support for Target Groups in the Proxy                                                                                                                     | false                                  |
 | PROMETHEUS_PORT        | 9091                                 | Port that the prometheus metrics are exposed on, defaults to 8000                                                                                                           | 8000                                   |
 | FORWARD_TARGETS        | false                                 | The Proxy will forward targets sent by Client SDKs to Harness Saas | false                                   |
+| REDIS_MAX_RETRIES              | 3   | Maximum number of retries before giving up. Default is 3 retries.               | 3   |
+| REDIS_MIN_RETRY_BACKOFF_MILLIS | 8  | Minimum backoff between each retry in milliseconds. Default is 8 milliseconds   | 8   |
+| REDIS_MAX_RETRY_BACKOFF_MILLIS | 512 | Maximum backoff between each retry in milliseconds. Default is 512 milliseconds | 512 |
+| REDIS_DIAL_TIMEOUT_SECONDS     | 5   | Dial timeout for establishing new connections in seconds. Default is 5 seconds        | 5   |
+| REDIS_READ_TIMEOUT_SECONDS     | 3   | Timeout for socket reads in seconds. If reached, commands will fail with a timeout instead of blocking. Default is 3 seconds. | 3 |
+| REDIS_WRITE_TIMEOUT_SECONDS    | 3   | Timeout for socket writes in seconds. If reached, commands will fail with a timeout instead of blocking. Default is 3 seconds. | 3 |
+| REDIS_POOL_SIZE | 10 | DEPRECATED: Legacy setting that has been kept for backwards compatibility, you can use `REDIS_POOL_SIZE_LITERAL` moving forward. This sets the Redis connection pool size to this value, multiplied by the number of CPU available. For example, if this value is 10 and you've 2 CPUs, the connection pool size will be 20. | 10 |
+| REDIS_POOL_SIZE_LITERAL | 50 | Sets the maximum number of socket connections to the literal value passed. For example, setting this to 10 means the connection pool size will be 10. If not specified, this will be set to the default value of 10 per CPU. | 0 |
+| REDIS_POOL_TIMEOUT_SECONDS | 4 | Amount of time in seconds that the client waits for connection if all connections are busy before returning an error. Default is 4 seconds (default ReadTimeout + 1 second). | 4 |
+| REDIS_MIN_IDLE_CONNS | 0 | Minimum number of idle connections, which is useful when establishing that a new connection is slow. | 0 |
+| REDIS_MAX_IDLE_CONNS | 0 | `MaxIdleConns` is the maximum number of idle connections. The idle connections are not closed by default. Default: 0 | 0 |
+| REDIS_MAX_ACTIVE_CONNS | 0 | `MaxActiveConns` is the maximum number of connections allocated by the pool at a given time. When zero, there is no limit on the number of connections in the pool. If the pool is full, the next call to `Get()` will be blocked until a connection is released. | 0 |
+| REDIS_CON_MAX_IDLE_TIME_MINUTES | 30 | The maximum amount of time, in minutes, that a connection may be idle. Should be less than server's timeout. Expired connections may be closed lazily before reuse. If 0, connections are not closed due to a connection's idle time. -1 disables idle timeout check. Default: 30 minutes | 30 |
+| REDIS_CON_MAX_LIFETIME_MINUTES | 0 | The maximum amount of time, in minutes, that a connection may be reused. Expired connections may be closed lazily before reuse. If 0, connections are not closed due to a connection's age. Default: 0 | 0 |
 
 
 # The Proxy Key V2

docs/feature-flags/use-ff/relay-proxy/relay-proxy.md

@@ -11,7 +11,7 @@ This topic describes the Harness Relay Proxy V1 and how to use it with Feature F
 The Relay Proxy V1 enables your apps to connect directly to Feature Flag services without having to make a significant number of outbound connections to FF services. The Relay Proxy establishes a connection to the Feature Flags configuration data and relays that connection to clients in an organization's network.
 
 :::info note
-The Relay Proxy Version 2 is now available from Harness! If you want to learn more, please go to the [Relay Proxy V2](./relay_proxy_v2.md) page. You'll find information regarding how to set it up, the key features and more. 
+The Relay Proxy Version 2 is now available from Harness! If you want to learn more, please go to the [Relay Proxy V2](/docs/feature-flags/use-ff/relay-proxy/relay-proxy-v2) page. You'll find information regarding how to set it up, the key features and more. 
 :::
 
 ## Why use the Relay Proxy?

release-notes/feature-flags.md

@@ -1,7 +1,7 @@
 ---
 title: Feature Flags release notes
 sidebar_label: Feature Flags
-date: 2025-07-16T08:09:25
+date: 2025-08-05T08:09:25
 tags: [NextGen, "feature flags"]
 sidebar_position: 11
 ---
@@ -26,7 +26,41 @@ Follow this template to sort your release notes into the correct headline:
 Harness deploys changes to Harness SaaS clusters on a progressive basis. This means that the features and fixes that these release notes describe may not be immediately available in your cluster. To identify the cluster that hosts your account, go to the **Account Overview** page. 
 :::
 
-#### Last updated: July 24, 2025
+#### Last updated: August 5, 2025
+
+## August 2025
+
+### Relay Proxy
+
+#### Version 2.0.14
+
+**New features and enhancements**:
+
+- Added support for additional environment variables to enable advanced Redis configuration. These provide greater flexibility for fine-tuning your Redis setup with the Relay Proxy. (FFM-12528)
+
+```
+REDIS_MAX_RETRIES
+REDIS_MIN_RETRY_BACKOFF_MILLIS
+REDIS_MAX_RETRY_BACKOFF_MILLIS
+REDIS_DIAL_TIMEOUT_SECONDS
+REDIS_READ_TIMEOUT_SECONDS
+REDIS_WRITE_TIMEOUT_SECONDS
+REDIS_POOL_SIZE
+REDIS_POOL_SIZE_LITERAL
+REDIS_POOL_TIMEOUT_SECONDS
+REDIS_MIN_IDLE_CONNS
+REDIS_MAX_IDLE_CONNS
+REDIS_MAX_ACTIVE_CONNS
+REDIS_CON_MAX_IDLE_TIME_MINUTES
+REDIS_CON_MAX_LIFETIME_MINUTES
+```
+
+For a full list and description of the available configuration options, see the [Feature Flags documentation](/docs/feature-flags/use-ff/relay-proxy/relay-proxy-v2#full-breakdown-of-configuration-options).
+
+**Maintenance**:
+
+- Upgrade the `go-redis` client library version from 9.5.5 to 9.11.0. (FFM-12528)
+- Upgrade dependencies to resolve an [OAuth2.0 vulnerability](https://github.com/harness/ff-proxy/security/dependabot/25). (FFM-12517)
 
 ## July 2025