-
Bug
-
Resolution: Done
-
Normal
-
4.14, 4.15, 4.16, 4.17, 4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
3
-
None
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 275, OSDOCS Sprint 276
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The Insights Operator documentation currently lists proxy configuration attributes incorrectly under dataReporting. Incorrect Configuration (as per documentation): dataReporting: httpProxy: httpsProxy: noProxy: Correct Configuration: dataReporting: proxy: httpProxy: httpsProxy: noProxy: Correction Needed: Update the documentation[2] to nest the proxy settings under the proxy key within dataReporting. [1] https://github.com/openshift/insights-operator/blob/release-4.18/docs/arch.md#how-the-insights-operator-reads-configuration:~:text=proxy%3A%0A%20%20%20%20httpProxy%3A%20http%3A//example.com%2C%0A%20%20%20%20httpsProxy%3A%20https%3A//example.com%2C%0A%20%20%20%20noProxy%3A%20test.org [2]https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/html/support/remote-health-monitoring-with-connected-clusters#insights-operator-configuring_using-insights-operator:~:text=httpProxy%2C%20httpsProxy%2C%20noProxy
Version-Release number of selected component (if applicable):
4.19
Actual results:
dataReporting: httpProxy: httpsProxy: noProxy:
Expected results:
dataReporting: proxy: httpProxy: httpsProxy: noProxy:
- links to
(2 links to)