Update RN with more details and add K3s options to the install-vm page

Author: ZdravkoDonev-redis

content/integrate/redis-data-integration/installation/install-vm.md

@@ -182,6 +182,18 @@ it without the `noexec` option. See
     ```bash
     sudo ./install.sh --installation-dir <custom-installation-directory>
     ```
+
+    **Advanced**: You can also pass custom K3s parameters to the installer using the `INSTALL_K3S_EXEC` environment variable. For example, to set the kubeconfig file permissions to be readable by all users:
+
+    ```bash
+    sudo INSTALL_K3S_EXEC='--write-kubeconfig-mode=644' ./install.sh
+    ```
+
+    You can combine multiple K3s options in the `INSTALL_K3S_EXEC` variable. See the [K3s documentation](https://docs.k3s.io/installation/configuration) for a full list of available options.
+
+    {{<warning>}}
+    Only modify K3s parameters if you understand exactly what you are changing and why. Incorrect K3s configuration can cause RDI installation to fail or result in an unstable deployment.
+    {{</warning>}}
     {{< /note >}}
 
 The RDI installer collects all necessary configuration details and alerts you to potential issues, 

content/integrate/redis-data-integration/release-notes/rdi-1-15-0.md

@@ -44,12 +44,19 @@ RDI now uses the native `JSON.MERGE` command instead of Lua scripts for JSON mer
 - **Support for sharded Redis databases**: RDI now supports writing to multi-sharded Redis Enterprise databases for the RDI database, resolving cross-slot violations when saving statistics.
 - **Enhanced processor performance metrics**: Detailed performance metrics are now exposed through the metrics exporter and statistics endpoint, with separate tracking for transformation time and write time.
 - **Resource management improvements**: Collector and processor pods now support configurable resource requests, limits, and node affinity/tolerations for better cluster resource utilization.
+  - The `collector` defaults to 1 CPU and 1024Mi memory (requests), with limits of 4 CPUs and 4096Mi memory.
+  - The `processor` defaults to 1 CPU and 512Mi memory (requests), with limits of 4 CPUs and 3072Mi memory.
 
 - **Leadership status monitoring**: New metrics expose leadership status and pipeline phase information for better monitoring of HA deployments.
+  - The `rdi_operator_is_leader` metric tracks the current leadership status of the operator: `1` indicates the instance is the leader, `0` indicates it is not the leader.
 - **Improved configuration validation**: More rigid validation for `config.yaml` and `jobs.yaml` files helps catch configuration errors earlier in the deployment process.
 - **Custom K3s installation options**: The installer now supports passing custom arguments to K3s installation for more flexible on-premises deployments.
+  - Example: `sudo INSTALL_K3S_EXEC='--write-kubeconfig-mode=644' ./install.sh`
 - **Workload Identity authentication**: Added support for Google Cloud Workload Identity authentication to Google Cloud Storage (GCS), eliminating the need for service account JSON files in many scenarios.
 - Processor performance metrics showing transformation and write times separately
+  - `{namespace}_processor_process_time_ms_total` - Total time spent in the processor (transform + write)
+  - `{namespace}_processor_transform_time_ms_total` - Time spent transforming data
+  - `{namespace}_processor_write_time_ms_total` - Time spent writing data to Redis
 - Enhanced statistics endpoint with new metrics for transform and process time
 
 ### Bug Fixes and Stability Improvements
@@ -58,12 +65,6 @@ RDI now uses the native `JSON.MERGE` command instead of Lua scripts for JSON mer
 - **Fixed Debezium unavailable values**: Addressed issues where `__debezium_unavailable_value` was appearing in Redis data.
 - **Improved operator stability**: Disabled operator webhooks by default to simplify deployments and reduce potential issues.
 
-### Documentation Improvements
-
-- **Oracle XStream documentation**: Added documentation on how to prepare Oracle databases with XStream for RDI.
-- **Flink collector documentation**: Added the `rdi-flink-collector` to the public documentation.
-- **FAQ for common issues**: Created a comprehensive FAQ with common issues and error messages to help users troubleshoot problems more quickly.
-
 ## Limitations
 
 RDI can write data to a Redis Active-Active database. However, it doesn't support writing data to two or more Active-Active replicas. Writing data from RDI to several Active-Active replicas could easily harm data integrity as RDI is not synchronous with the source database commits.