Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 1794825: Operator-defined namespace that requests monitoring should fully warn user of implications of enabling #4120

Merged
merged 1 commit into from Jan 31, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -5,9 +5,11 @@ import { match } from 'react-router';
import { ActionGroup, Alert, Button, Checkbox, Tooltip } from '@patternfly/react-core';
import {
Dropdown,
ExternalLink,
Firehose,
history,
NsDropdown,
openshiftHelpBase,
BreadCrumbs,
MsgBox,
StatusBox,
Expand Down Expand Up @@ -348,10 +350,24 @@ export const OperatorHubSubscribeForm: React.FC<OperatorHubSubscribeFormProps> =
onChange={setEnableMonitoring}
isChecked={enableMonitoring}
/>
<small>
Note: Enabling monitoring will allow any operator or workload running on this namespace
to contribute metrics to the cluster metric set.
</small>
{props.packageManifest.data[0].metadata.labels['opsrc-provider'] !== 'redhat' && (
<Alert
isInline
className="co-alert pf-c-alert--top-margin"
variant="warning"
title="Namespace monitoring"
>
Please note that installing non Red Hat operators into openshift namespaces and
enabling monitoring voids user support. Enabling cluster monitoring for non Red Hat
operators can lead to malicious metrics data overriding existing cluster metrics. For
more information, see the{' '}
<ExternalLink
href={`${openshiftHelpBase}monitoring/cluster-monitoring/configuring-the-monitoring-stack.html#maintenance-and-support_configuring-monitoring`}
text="cluster monitoring documentation"
/>{' '}
.
</Alert>
)}
</div>
)}
</>
Expand Down