Bug 1794825: Operator-defined namespace that requests monitoring shou…

…ld fully warn user of implications of enabling
openshift · Jan 30, 2020 · 08cc849 · 08cc849
1 parent 009dd9d
commit 08cc849
Showing 1 changed file with 19 additions and 0 deletions.
diff --git a/...ackages/operator-lifecycle-manager/src/components/operator-hub/operator-hub-subscribe.tsx b/...ackages/operator-lifecycle-manager/src/components/operator-hub/operator-hub-subscribe.tsx
@@ -5,6 +5,7 @@ import { match } from 'react-router';
 import { ActionGroup, Alert, Button, Checkbox, Tooltip } from '@patternfly/react-core';
 import {
   Dropdown,
+  ExternalLink,
   Firehose,
   history,
   NsDropdown,
@@ -352,6 +353,24 @@ export const OperatorHubSubscribeForm: React.FC<OperatorHubSubscribeFormProps> =
             Note: Enabling monitoring will allow any operator or workload running on this namespace
             to contribute metrics to the cluster metric set.
           </small>
+          <br />
+          <br />
+          <Alert
+            isInline
+            className="co-alert co-alert--scrollable"
+            variant="warning"
+            title="Namespace monitoring"
+          >
+            Please note that installing non RedHat operators into openshift namespaces and enabling
+            monitoring voids user support. Enabling cluster monitoring for non RedHat operators can
+            lead to malicious metrics data overriding existing cluster metrics. For more
+            information, see the{' '}
+            <ExternalLink
+              href="https://docs.openshift.com/container-platform/4.2/monitoring/cluster-monitoring/configuring-the-monitoring-stack.html#maintenance-and-support_configuring-monitoring"
+              text="cluster monitoring documentation"
+            />{' '}
+            .
+          </Alert>
         </div>
       )}
     </>