docs(power-monitor): point to advanced configuration doc

Rename configuring-kepler.md to guides/custom-configmaps.md to better
reflect the content, which focuses on advanced configuration using
custom ConfigMaps rather than general PowerMonitor configuration.

Signed-off-by: Sunil Thaha <[email protected]>

Author: Sunil Thaha

docs/user/README.md

@@ -34,7 +34,7 @@ Choose your platform to begin:
 Once installed, learn how to use Kepler Operator:
 
 - **[Creating PowerMonitor Resources](guides/power-monitor.md)** - Deploy and configure Kepler on your cluster
-- **[Configuration Options](configuring-kepler.md)** - Deep dive into PowerMonitor configuration
+- **[Custom ConfigMaps](guides/custom-configmaps.md)** - Advanced Kepler configuration with custom ConfigMaps
 - **[Validating Prometheus Integration](guides/validating-prometheus-integration.md)** - Verify Prometheus is scraping Kepler metrics
 - **[Setting up Grafana Dashboards](guides/grafana-dashboard.md)** - Visualize energy metrics
 - **[Upgrading](guides/upgrading.md)** - Upgrade the operator (Helm and OLM)

docs/user/configuring-kepler.md renamed to docs/user/guides/custom-configmaps.md

@@ -260,7 +260,8 @@ If the DaemonSet doesn't roll out after updating the ConfigMap:
 
 ## 📚 Related Resources
 
-- [PowerMonitor API Reference](reference/api.md#powermonitor)
+- [PowerMonitor Guide](./power-monitor.md) - Complete PowerMonitor configuration guide
+- [PowerMonitor API Reference](../reference/api.md#powermonitor)
 - [Kepler Configuration Reference](https://sustainable-computing.io/kepler/usage/configuration/)
 - [Kepler Documentation](https://sustainable-computing.io/)
 

docs/user/guides/power-monitor.md

@@ -265,6 +265,8 @@ spec:
 
 The ConfigMap must exist in the same namespace as PowerMonitor components.
 
+For detailed examples and best practices on using custom ConfigMaps, see the [Custom ConfigMaps Guide](./custom-configmaps.md).
+
 ## Common Use Cases
 
 **Note**: All examples below use the required name `power-monitor`. You cannot create multiple PowerMonitor resources with different names.
@@ -468,6 +470,7 @@ For more troubleshooting guidance, see the [Troubleshooting Guide](./troubleshoo
 
 ## Next Steps
 
+- **[Custom ConfigMaps Guide](./custom-configmaps.md)** - Advanced Kepler configuration with custom ConfigMaps
 - **[Grafana Dashboards](./grafana-dashboard.md)** - Visualize Kepler metrics
 - **[Troubleshooting Guide](./troubleshooting.md)** - Diagnose common issues
 - **[API Reference](../reference/api.md)** - Complete PowerMonitor API specification

docs/user/guides/validating-prometheus-integration.md

@@ -501,7 +501,7 @@ helm upgrade prometheus prometheus-community/kube-prometheus-stack \
 Once you've validated that Prometheus is scraping Kepler metrics:
 
 - **[Set up Grafana Dashboards](./grafana-dashboard.md)** to visualize the metrics
-- **[Configure PowerMonitor](../configuring-kepler.md)** to adjust metric levels and collection settings
+- **[Custom ConfigMaps](./custom-configmaps.md)** to adjust metric levels and collection settings
 - **[Set up Alerts](https://prometheus.io/docs/alerting/latest/overview/)** for abnormal power consumption
 
 ---

docs/user/installation/kubernetes.md

@@ -225,7 +225,7 @@ For complete setup and troubleshooting instructions, see:
 Now that the operator is installed, you can:
 
 1. **[Create a PowerMonitor resource](../guides/power-monitor.md)** to deploy Kepler
-2. **[Configure PowerMonitor](../configuring-kepler.md)** for your specific needs
+2. **[Custom ConfigMaps](../guides/custom-configmaps.md)** for advanced Kepler configuration
 3. **[Set up Monitoring Stack](./monitoring-stack-kubernetes.md)** (optional) - If you want to visualize metrics
 4. **[Validate Prometheus Integration](../guides/validating-prometheus-integration.md)** (if using Prometheus) - Ensure metrics are being scraped
 5. **[Set up Grafana dashboards](../guides/grafana-dashboard.md)** (if using Grafana) - Visualize metrics